Pulse not working for specific app

Hi gauche,

Please let us know the name of your application and what platform Pulse is being set up with (e.g. iOS, Android, Xamarin).

-Jason Fauchelle

Thanks gauche,

So far it looks like our api has not received any messages from the QUT app, suggesting that it is an issue in the provider. If you run your code for the application (via XCode or deployed to a test device), are you able to get Real User Monitoring data showing in your QUT or/and Raygun Playground apps?

-Jason Fauchelle

Yes sorry, I meant Visual Studio.

When you get a chance, please run the code for your QUT application, pointing at either "Raygun Playground" or "QUT" (or ideally try both if you don't mind the QUT app having a bit of local data) and this will help us narrow down if anything has changed. Also, let me know if Raygun outputs anything into the Visual Studio console.

-Jason Fauchelle

Hi gauche,

Apologies for the delayed reply. Thanks for trying out your app locally.

I'm going to test a new theory a colleague suggested and get back to you soon.

-Jason Fauchelle

Hi gauche,

Ignore my previous comment, the test did not reveal any issues.

So it sounds like the only difference is where the application is being run from - it works fine when running locally, but not when downloaded from the store. The fact that nothing is coming from either your iOS or Android apps suggests there may be a common issue among them. What we do know is that no messages are being sent from your production app to our api, meaning the issue is occurring within the app.

What we recommend now is that you do some further troubleshooting in your app to narrow down on the issue. Since the issue is only present in the app downloaded from the store, debugging this issue will be a little tricky. The Android app store provides the ability to release alpha and beta versions of your app. What you could try is use the RaygunClient to send a pulse event manually using the sendPulseEventTiming method and see if that shows up in the app. You may want to point this at your Raygun Playground application. Then deploy this modified app as an alpha or beta to the Android store and test that out.

If you could send the Raygun setup code you saw when decompiling the APK, I could see if anything looks out of place, though I can't think of anything setup wise that would work locally and not in production - especially since Crash reporting is working fine from the same setup.

-Jason Fauchelle

Great to hear you found the root cause of the issue. Apologies for the inconvenience and thanks for getting back to us about it. We'll get this sorted in the next package release.

-Jason Fauchelle

It's hard to say when the next Raygun4Net release will be sorry. It would likely be a month or two. Just to clarify, is there a workaround such as linker options that allows Pulse to function in your app in the meantime?

-Jason Fauchelle