Google Play Service out of date - android

I am testing my app on 2 devices:
Samsung SM-T211 (Android 4.1.2) and Galaxy Nexus (Android 4.3)
I have no problems on the first one, but on the Nexus I get a
Google Play Service out of date. Requires 4242000 but found 315830
How can that be?

Related

App in google play not showing on newest samsung galaxy's

I was looking at newest phones at the store today and found out that my app cant be seen in google play on S10, S10+, S10e, S9, S9+ and NOTE9. Other Motorola, Huawei, Honor... works fine. And its strange because on my emulator Pixel2 with Android Pie and with google play store it works fine too. In google play console/release management/device catalog it says that all newer galaxy phones are supported but in reality they are not. Target API in my app is 27 but that shouldn't matter, wright!?
Anyways, how do I fix that?

Instant Apps not working on any Pixel XL devices

I've built and published an instant app for my company but it doesn't work on my own Pixel XL, my wife's Pixel XL, my manager's Pixel XL, or his girlfriend's Pixel XL. We see the instant app "speed bump" window (its just blank with spinner) popup very very briefly for under half a second then it offloads to the website. All of our phones properly identify buzzfeed tasty as an instant app in Google search but the behavior is the same. We have tried a number of different known instant apps and none of them work. All devices are running Oreo.
We have verified we are running the latest Play Services. We have toggled instant apps on and off multiple times. Chrome, Play Store, and Play Services for Instant Apps are fully installed and up to date.
For testing I used a Galaxy S7 Edge (Nougat) that worked flawlessly. We have verified that the published instant app shows up for other Galaxy S7 users.
It's a shame that Google's own devices are having the most problems running their own latest and greatest services.
Any idea what the problem could be?

Error 505 while installing on Lollipop devices

I am a developer and recently published my new application My VIT on Play Store. Everything is working fine except a small bug in Android Lollipop devices. Whenever my users are trying to install app from play store in their devices, they get a 505 during the time of installation.
The app is running well on Kitkat and many other Lollipop devices. Some devices like nexus 6, nexus 7 2013, htc one m8, yu yuphoria are facing problems. I contacted Google Support, but they provided me with solutions I already performed.
I have cleared my Play Store data, Play Services data, download manager data, reset my date/time and re-added my Google account. Still no luck. I think it's a development issue because my other app is running fine on those devices.

Samsung devices have a strange version of Google Play Services and it doesn't work correctly

I am using Activity Recognition API available in Google Play Services.
I've tried using Google Play Services 5+ and Google Play Services 6+ (using the new API with GoogleApiClient) on Android 4+ and Android 5+. Everything works great on different kinds of devices, except Samsung Galaxy Note 4
(Announced 2014, September)(Can not test on other Samsung devices.)
The problem is that:
Samsung Galaxy Note 4 has Google Play Services 5.0.89 (currently the
last version is 6.5.99) (and it's not possible to update it)
Activity Recognition API doesn't work (it's available, just
doesn't trigger needed recognition events)
Does anyone faced the similar problems on any Samsung devices?
How to resolve it?
Thanks.

Activity recognition not working on several devices

the sample code from http://developer.android.com/training/location/activity-recognition.html
doesn't work in Nexus S and Motorola droid devices (and probably on other devices also),
confirm working on Nexus 7 2013 and Samsung Galaxy Young,
this occurs after update to latest play services 5.0.89, in my recall two months ago, it works fine on all devices,
try to switch using GoogleApiClient, no luck
confirm working after enable network Provider on location access, I think this is a bug on play service

Categories

Resources