I flashed my genymotion device and after, I got this error.
"An error occurred during the installation of google+ Please uninstall the app and then install it again"
To elaborate.
I created a new device, this one at the top highlgihted.
Google Nexus 4 5.0.0 API 21
I read this good and (as of writing), up to date answer here about installing google play services on it Google Play Services in Genymotion on Lollipop (Android 5.0)
So I started it, did adb devices saw the device listed there.
Dragged this on Genymotion-ARM-Translation_v1.1.zip
I did adb reboot
I dragged this on gapps-lp-20141109-signed.zip
I did adb reboot
Then I got this screen (it looked good though I knew it might not work so I took a screenshot as "evidence"!)
Then on going to google play store, or on unlocking the screen.. and periodically..or whenever it is, I got/get this screen
It did ask me to register with google signing or or creating a new account when going into the play store, and I did. Though I still get that google+ error message from time to time.
I can use android studio's emulator api 21 in the meantime as while it doesn't have google play store, it does seem to have google play services such that various apps can run, but i'd be interested in having genymotion running without error with google apps services too, particularly as having the google play store, as it does, is good so if it can be without this error then all the better.
You need to be patient through the error messages, and manage to sign-in to the play store and update Google+.
After, you should get a notification saying you need to update Google Play Services, do it as well.
It can be annoying with the error message popping all the time but you just have to go through this once :).
Reboot the device after and it should work.
Related
I published my mobile app in Google play console recently. Regarding crash logs in Android vitals I'm doing bit investigation on it and I have some doubts,
Is Google play console capable of log offline crashes when device back to online ?
I could see the crashes updated in Google Play console even I'm working in development apk with my real mobile device, How Google Play console logs the crashes occured it local apk, it is only for the apps downloaded from Google Play store right ?
Please anyone clarify my above questions since I'm new to mobile app development area
.
Yes, Google will collect crashes even when they occur offline.
Google will collect crashes even if the app is not installed via Play Store. You can however filter those crashes in the Play Console directly by adding the filter "Installed from Google Play":
I created a standalone smartwatch app for Wear OS. I use a Huawei Watch 2 4G for testing. I now want to have it in the beta track on Google Play Store so that users can test it. I've created some smartphone apps already and put them in the Play Store, so I'm used to the process. What I did so far:
Created entry on Google Play Console
Added a release to the open beta track
Filled all necessary stuff
Published the app and got the URL to participate in the beta test
Opened the URL while logged in with my test account and agreed to become a tester
Wiped the smartwatch and copied the same account to the watch during setup
Now I don't know how to install the app from the Play Store. On a smartphone I would simply open the URL in a browser and would be able to install it from there. What I tried so far:
Searching for the app name and for the package name on the Play Store on the smartwatch, but it can't find it.
Opening the Play Store entry in a browser and click the install button, but it says that I have no devices.
Opening the URL on the paired smartphone, but it only says that the device is not compatible.
How can I install a standalone Wear OS app that is in the open beta track on Google Play Store?
As suggest in #tofferj 's comment I simply had to wait a few more hours. I'm now able to find it by simply searching for the app name in the Play Store on the smartwatch.
Seems like the status "published" on the Google Play Console doesn't mean that it's already in the search index.
I am making a standalone wear app and have uploaded the wear apk in beta testing
and have also added account in tester list but still the app won't appear in
wear play store
Can someone help me with this? i m new to android wear
I assume you are tring to use a closed beta distribution mode.
If you want your app to be found by simple search on the Play Store use an openBeta instead (everybody can search your app).
However, if you still have difficulties finding your app on the watch store you can use the following method starting directly at point (3).
If you need to stick with closed beta, you need to install the app trough the browser of your PC/MAC.
Use the test link of your app:
https://play.google.com/apps/testing/{YOUR_PACKAGE_NAME}
(Make sure you are logged in to the Google Play in your browser with the Google Account you authorized as a beta tester)
Accept to become a beta tester, and click on "Download the {YOUR_APP_NAME} app on Google Play" or Search it directly in the store.
Once you are in the Google Play listing page of your app, install it by clicking on the install button and
selecting your device:
So I am trying to setup Google Play Games Services in the Google Play Developer Console.
This worked for me yesterday.
Today however, when setting up another app, and trying to link an android app to the games services, I get this error:
An unexpected error occurred. Please try again later. (4800001)
I got this in:
Google Play Developer Console -> Games Services -> [game] -> Linked Apps -> STEP 2 Authorize your app.
This happens regardless which key I try, my release key, or my debug key.
I don't understand why this would be happening, as it was working yesterday, albeit for an app without real-time multi player. The app I am trying to setup now needs real-time multiplayer, but I'm not sure whether this difference is the cause of it. Maybe servers at google are down?
I get the error each time I try, regardless which browser I use, or which OS. I tried on Ubuntu Firefox and OSX Safari.
This was a temporary breakage in the Google Play Developer Console.
They fixed it today, by rolling back changes to the console, see:
https://github.com/playgameservices/android-basic-samples/issues/153#issuecomment-134749998
I opened https://console.developers.google.com/ page and successfully registered my app there while I was having same issue as you.
I have made a Windows Phone app (for WP7.1) that uses BackgroundAudio for streaming, nothing too complicated. It was approved and made available for download in the store. However it no longer works, i.e. the app worked in debug+release when run from VS2012, and I assume the .xap I uploaded worked since microsoft approved it (they rejected it once and I was able to reproduce and fix the bugs they reported).
When downloaded the app simply bails on load on WP8 (lumia 820) i.e. flips back to the tiles immediately.
On WP7 (lumia 800) but the playbutton ignores input, however it downloads and displays the playlist, so some kind of functionality+network connection works.
I have tried the basics: installing using the application-deployment tool (app working), running the "Store Test Kit" which reports some slowdowns in the UI animations, but nothing serious (I hope).
Any ideas how to reproduce ".xap approved and downloaded from store but not working" or getting debug info from the phone without VS? Or any other things i can try out?
Every time your app crashes it will be logged and reported on your Windows Phone Dev Center Account. Just go in there and export the details to excel. Get the stack trace and put it in here. Maybe we can help.
The very first thing i can tell you is the opening page has some exceptions and that too it doesn't go well with some phones. Seriously there are concerns when a wp7 app is ported on wp8 device and vice-verse. To the extent of my knowledge there might be some binding issues. make sure you got the binding class to be public. And just as #AMR mentioned go the dev center and export the stacktrace. Try resolving them. Moreover if an app get certifies, it doesn't mean it is completely error free. The tests are limited to very coomon errors only.