I missed the memo on the Oculus Go not supporting Firebase (because it doesn't come with Google Play Services installed) and got the Firebase Auth system working for my VR game with the SDK version 5.3.0. When I upgraded to SDK version 5.3.1 I got a system dialog "{my app} won't run without play services which weren't supported by your device". I found out Firebase updated the required Google Play Services version when they updated the SDK to 5.3.1, so my question is: where did the outdated GPS come from and can it can relied on (hah!) to stay there?
Based from Eveything you need to know to develop for Oculus Go documentation:
Gear VR compatability
Google Play Services: Unlike the Samsung Galaxy devices that run Gear
VR, Oculus Go does not ship with Google Play Services installed. You
cannot rely on Google Play Services (e.g. Google Firebase, Google
Cloud Messaging, etc.), or third-party libraries that depend on Google
Play Services (e.g. OneSignal) when running on Oculus Go.
Therefore some applications have automatically opted-out of distribution in Oculus Go because they contain compatability problems. You can opt an application back into Oculus Go distribution by fixing the compatibility errors (e.g. dependency on GPS) and uploading a new build.
Related
What steps do I need to take when I have troubles trying to use an app I created and try to run it on the latest Samsung Tab A 10.1? I tried to start the app, the message displayed is :
This application requires the latest version of ARCore
So I tapped the continue button. I was taken to Google Play. The title says "Google Play Services for AR". Then below that it says:
Your device isn't compatible with this version
Does anyone have a solution, please?
Firstly check whether the device you are using has the ARCore support:
It was indeed an easy experience in terms of building and running the app on the IOS device, iPhone 10. There were no complications in activating the ARkit in the devices since they were built in like the documentation mentioned. It was particularly gruesome in building the AR app on an Android device. As per the documentation the Android devices such as Samsung Galaxy A70S is compatible with ARCore.
Firstly the app simply crashed on installing into the device
As a part of the workaround, I looked for installing, "Google Play Services for AR" on my play store which simply didn't show up
I directly tried to install the app "Google Play Services for AR" through google but it failed with the message, the app is not compatible with my device.
I did a trial and error with installing the "Google Play Services for AR" apk directly from https://www.apkmirror.com/apk/google-inc/arcore/, specifically https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-13-19100710-release/google-play-services-for-ar-1-13-191007106-android-apk-download/ to my Android device to enable ARCore which supported 64-bit processor
The app was however still crashing due to the 403 forbidden IP error on persisting the data
The issue got resolved on adding my public IP to azure rules
We have an android app on Play Store for last 2 years. We are trying to connect the Google Drive API using play services inside the app.
Things are working fine for all the android OS except 4.4.X. In 4.4.X OS devices while trying to login to the Google Account most of the users are getting the error (as reported by them) like :
" is having trouble with Google Play services.Please try again."
Does anyone know how to fix this issue?. This is Not reproducing on all 4.4.X devices.
If you are having troubles with your virtual devices when running things like Google maps etc.; try creating a new virtual device with Google Play Store incorporated
On your Android phone, go to Settings.
Click on Apps.
Click Google Play services.
Click on Permissions.
Ensure all permission settings are turned on.
I've had the same issue as reported above after updating my app dependencies from com.google.android.gms:play-services-maps:15.0.1 to ..:16.1.0 (or ..:17.0.0). The problem for was that the installed version of Google Play Services on my device (a Zebra TC51 running Android 6.0.1 in this case) is rather old and is managed by our customer using a mobile device management solution (MDM) that is very conservative. Rolling back to ..:15.0.1 or updating Google Play Services to the latest version would both solve this issue for me. Sadly, I cannot force our customers to update Google Play Services (although I'd like them to update obviously).
Reproducing this is straightforward by just installing an older Google Play Services (download the July 2018 version for example, v12.8.74. Set your dependency to 16.0.1 or newer and you'll get the above error message.
I haven't been able to find an overview that lists the compatibility between versions of the installed Google Play Services APK and which versions of the com.google.android.gms:play-services-maps dependency are supported.
Also, have a look at the Overview of Google Play Services where it is explained how the included dependency (in your app) and the installed client library (on the device) depend on one another.
Make sure your Google Play Services is updated
For me worked: Settings > Apps and Notifications > Google Play Store > Permissions > All ON
I fixed this by following the instructions on setting up Firebase on a new project. I encountered the "Try again" prompt until I added firebase-core to the project.
Opening google maps once and the trying my map fixed the problem
I recently began learning how to create Google Maps activities in Android app development, and have stumbled onto an issue with Google Play Services. Whenever I set my gradle build dependency to compile 'com.google.android.gms:play-services-maps:11.0.4', which is the most recent version of play-services-maps, the emulator screen gets stuck on the following view upon running my maps app:
I have allowed the app to sit there for over an hour, and nothing has changed or updated. As I've read in other StackOverflow questions, I can get the app to properly function by setting my gradle build dependency to an older version, such as compile 'com.google.android.gms:play-services-maps:9.0.0', but this limits my ability to use newer Android features and APIs in my apps, such as FusedLocationProviderClient.
I am running on Nougat 7.1.1, and have installed the following SDKs in an attempt to solve this Google Play Updating issue:
Android SDK Build-Tools
Android SDK Tools
Google Play APK Expansion Library
Google Play services
Support Repository > Google Repository
I haven't found any StackOverflow threads specific to this "Google Play services are updating" message. What can I do to resolve this issue?
Use API 24 or API 26 Android Emulator system images and you should be good to go. API 25 does not have the latest Google Play Store app pre-installed yet. Note on the screen shot that only these images are "Google Play" versions.
In addition to #Jamal Eason's answer, you may use Nexus 5 and Nexus 5X emulators which have Play Store. Check here. You may also try running on real android device connected via USB that supports google maps and having google play service installed.
Where can I download the Google Play Services SDK 7.8 even if it is a beta?
I need it for the new Google Proximity Beacon API.
I can not get it with Eclipse or Android Studio.
It seems, that some have it allready.
It is here now: Google Play Services 7.8
The APK already started rolling out, just checked and my Nexus 5 and it's already on 7.8.
The APK is just one part though, and if you want to develop apps with Google Services, you also need the client library:
https://developers.google.com/android/guides/overview
The client library (which is what you add to your app to access the Play Services APIs, and which will later talk to the APK on the phone) is something you download via the Android SDK Manager. The latest available revision is still 25 though, which corresponds to Play Services 7.5.
TL;DR, we're still waiting for Play Services 7.8 with the Nearby API to be released in full.
Client library is released to developers when the rollout of Play Services to most of the devices is done. They are probably doing some staged rollouts this time as well, so we need to wait a little bit more.
I recently updated the android google sdk with the latest version of google play services library (7.5).
Since the update I cannot run my app on emulator : when I click sign in button a pop up appears saying that I need to install the latest version of google play games app.
Of course I'm using the latest google apis for the emulator image. What happens? Did I miss something?
It turns that now google play services is linked to google play games app. It seems that if you don't have the app installed you cannot run the game that uses google play services. The emulator of course come without the games app I have to manually install the apk and now it works again. :-o