@jonathanpeppers Thought you would want an update, In the end it was a combination of the conditions my users were in, and me apparently scuffing up.
Part 1. Apparently my users were often times in an area where they only barely had a 3G connection, Thus the default timeout time of the http client was too short for requests to complete, Solution, make the timeout a bit longer.
Part 2, Me scuffing up,
Apparently i had some debug code in the server on certain requets, IE the ones that are called in onresume and onstart, that in certain edge cases, (No/wrong permissions on database/tables,) it would return an empty string, Now i allowed the Json parsing to go through if the result was not
null and it was not "offline", So the deserializer got passed an empty string, the model it had to deserialize to had only nullable values so it passed, but then if i tried to get an element of the model it would nullref. Fixed by not being dumb and returning null instead. This was also the case in my async GET manager. that would return an empty string instead of null.
Use the custom error tracing that appcenter provides,
Call the clients that its crashing for.
Hi folks. We're looking to move a discussion from StackOverflow somewhere where we might get help. Basically for Android since upgrading Xamarin.Forms components we're no longer getting push notifications handled when the app is stopped (not force stopped, not in Doze mode). Worked for earlier 3.? versions, not anymore. The SO conversation is in the comments section here https://stackoverflow.com/questions/59582314/how-can-i-receive-a-push-notification-when-my-xamarin-android-app-is-stopped
Have folks here in the last 3 or 4 months run into any known Firebase/Xamarin issues that might help? Is this a forms thing or OK to discuss here?