I am working on a xamarin android application. When I add Google Play Services from components in my application it continuously builds and never stops.
What could be causing this?
The cause it's Google Play Services itself, unfortunately once you added it will take several minutes to build. Try removing it and add it as a nuget, I don't think this will solve the entire problem but at least it will let you build the app, but remember it will still take it time to do it.
Related
How do I make my sideload only android app check for updates on every launch
For example make it go to example.com/latest.txt and compare the versions and then download it
Or another solution that doesnt involve play services.
I've tried looking this question up but didn't find anything of use
Recently I updated my app by adding a couple of functions. In addition, I recreated the project since I had problems with app support for Android devices below Lollipop. After update and upload on Google Play, I update the app over Google Play on my separate real device (non test device) and it just keeps crashing (by opening it closes right away) without any errors on device. Google Play Console reports under "Crashes" IllegalStateException at
package.d.a (Unknown Source:73). However, the d.a package name is totally unknown for me, because I do not have that in my entire project.
package.MainActivity.onResume (Unknown Source:8). At this 8th I have an Import which would never cause an exception.
I guess that not only me, but some another users, who already updated the app, have also the save problem. However, I just generated a signed apk of my app and installed it on my real device (non test device), but for this step I needed to remove the app downloaded from Google Play before manual installing. This approach worked and the app does not crashes any more and works properly without problems.
I think, for users who download the app for the first time ever, this problem does not occur for them. How can I find out the cause of the problem?
Here is my app. If the app works for those who downloaded it after reading this post, please send me some short feedback using the built in Send Feedback in the app just to ensure the app functionality.
If you use proguard you need to add the mapping file to your console
If you use ProGuard to optimize and obfuscate your APK files, you can upload a ProGuard mapping file for each version of your app on the Play Console to deobfuscate your crash stack traces and help you better analyze your app's crashes.
Important: Only ProGuard mapping files are supported for deobfuscation.
Do you use any kind of testing with your app? You can try testing it on Firebase Test Lab, especially the Robo Tests, which try to crawl and use all app interactions.
They can help in detecting any faults or issues early on before releasing the app to the market.
You can also use Firebase's Crashlytics to detect crashes and get more details on the crashes.
Hope this helps.
I found the solution. In my case, I just needed to clear the cash of the app in the device settings. It helped to run the app again. However, there could be another solutions or even problems with such kind of app crash.
I had a expo project, and due to some limitations i have detached
I added firebase to the project using react-native-firebase package and it needs some native code modifications
After many head shake, finally i ran it on the emulator successfully, But it ask to update google play unless the app won't run
In our region user doesn't update it regularly so it leads to bad UX.
I know its due to using google play service newest version , But is there's a way to use google play service low version with same functionality firebase provide for the top version? if not what kind of feature i will lose ?
I want to be able to detect the first run of my app before it has been updated by Google Play. (Trust me, this is a legitimate scenario.) Is there a way for me to keep Google Play/Android from updating the app before it has been run at least once?
You can create 2 apps, one that triggers the installation of the other via Intent. That way, you are sure the first one was run before installing the second.
I spoke with an engineer from Google. There is not currently any means to absolutely guarantee that an app is run before it is updated by the Play Store.
The code builds and runs but I am getting Google Play services issues as follows. I do not know what I am missing. I am using Xamarin Android Player (XAP) emulator.
In the Reference
Xamarin Android Player was deprecated some time ago, so we would not advise using it anymore as it will no longer be updated.
Having said that, we do have some old instructions here which may assist with this question: https://university.xamarin.com/resources/how-to-install-google-play-on-android-emulator
One of the motivations of XAP was to make it easy to have a well-performing emulator. Moving forward, we suggest using AVDs from Google which are now just as fast thanks to HAXM: https://developer.xamarin.com/guides/android/getting_started/installation/accelerating_android_emulators/