ERROR MESSAGE:
You not have a proprer app for viewing this content.
This Is not an Apk Problem, Nor a Signing Problem, Some Devices, Especially Samsung ones have an App Management Tool built-in. And Most Users don't even know about such thing. These App Management Features are just Messing with Google Play Store to Kepp the Device Alive and Prevent Any Crash.
But there is a setting in Samsung devices which gives the user option to deactivate this "Management" tool.
Also, If you have Published your Application on Google Play, Go your Google Play Console, There is an Option which tells you on Which devices your App can be installed and Used. It gives you a very high precision estimate of Device Reachability.
Your APK is Fine, Don't Worry.
Related
We are building an app in Unity for the Samsung S21 specifically, and we are noticing an interesting bug that resembles the following: https://issuetracker.unity3d.com/issues/android-not-enough-storage-space-to-install-required-resources-error-when-building-app-bundle-with-split-application-binary.
We have isolated it to phones that are "Fully managed" with Samsung Knox, and have noted that this occurs across all apps made with Unity, including major commercial releases on Google Play. This does not appear to be an issue with non-Unity apps.
After a factory reset, our app installs fine, but once it is updated or uninstalled and reinstalled we get the message "Error: Not enough storage space to install required resources." I have noticed that certain folders do not delete after the app is uninstalled--specifically /files/il2cpp and /files/Unity, and I cannot delete these on Knox-protected phones, while I CAN delete these folders on standard devices.
My Knox security settings say "User Deletion: Disallow."
I know that Knox is the issue here, but I am curious if anyone has any explanation what in particular with Unity is causing the problem. My suspicion is that this is because my Knox security settings do not allow me to delete, but it is interesting that this only seems to be the case in Unity apps as apps not developed in Unity (NBA Live is an example) uninstall and install fine. It is also worth noting that this all seems irrespective of the link I put above with the initial bug that claimed it was related to splitting the application binary.
We determined that using the Managed Google Play store only for downloads does not produce the issue. Any downloads from the commercial store--specifically Unity apps--will cause this issue. There is no workaround for this. If the organization with which you are working would like to be able to install a specific app on a phone with an account managed through Knox it must allow the specific app on the Managed Google Play store.
So, My app has run fine on all 13 devices according to pre launch report of play store, but does gave warning and in the performance section, on device of Samsung Galaxy S3, it says, no performance data is available for this device, any idea, why that can be issue and can play store not let me publish my app because of that warning,
Screenshots-
Google Play Console performance report data requires that the application be installed and used on any device. Detailed information is here
Are you sure your application is opened in Galaxy S3? I think your application is downloaded Galaxy S3 device but does not opened.
I've implemented Fabric (Crashlytics) in my app. Since yesterday I started an internal test on the Play Store. I created a new APK with a new version number. Only two people have been added to this internal test (which includes myself and a coworker). This morning I got some crashes from Fabric. But these crashes are from unknown phones: A rooted Samsung Galaxy S5 on Android 4.4.2 and a Samsung Galaxy J7 on Android 6.0.1. Where are these crashes coming from?
Edit
Internal testing on the Play Store is new. It is like Beta or Alpha builds (so only available for testers added to it).
I suspect this is from Google's pre-launch report.
When you upload an APK to an alpha, beta or testing track Google automatically runs your app on a number of devices to test quality.
We've experienced this on multiple projects too.
We assume that some third party stores, like apkpure, grabbed our apks from the playstore to list them in their store.
So those logs will either be from their internal testing devices, or from users that installed the app from the third party store.
We've found that all of our apps that have mysterious logs from unknown rooted devices are listed in one ore more third party stores.
But again, this is only an assumption.
I am using an android POS mini device on which I have installed my android app which uses google play services. I also have installed play services version 11.7.44 and play store version 8.4.40 by myself. Because it doesn't provide this 2 apps by default.
In my project I use:
compile 'com.google.android.gms:play-services-base:10.2.0'
And also services.
Sometimes my app stops working and doesn't even throw any error. Every time I have to reset my pos device to get over this error. I tried by clearing cache and other stuff as well. Is there any option to get rid off from such things?
In my minipos device its return null the session after some transation so how can i sloved it.
Google won't allow Google Play services on Google Play on a device which is not Android Compatible and passed the compatibility test suite (CTS). (source).
Self-installing Play services and Play might not be the cause, it might be a symptom of a device which is not truly Android compatible. Can you provide more details of your device in the question?
Any Android device which stops an app you would expect to provide errors in the log. This is also a sign the device is not fully android compatible.
I'd suggest testing your app in the emulator (which does allow Google Play services) and configure the emulator to be as close as possible to your device. That at least will give a stack trace if your app crashes, and allow you to debug.
There is an app on Google Play called SafetyNet Helper Sample. This will connect to a Google service called SafetyNet and tell you if the manufacter has passed CTS tests for the device. If they manufacturer hasn't then they aren't allowed to describe the device as "Android Compatible" (source), even if it is based on the Android source code which is open source.
I googled around and tried to find out something about the new Samsung App Store. I built an App for Google Play and I wonder if I can deploy it to the Samsung App Store.
The Android SDK isn't specially built for Google Play I guess. But looking at the Samsung SDK docs it seems quite different from the standard SDK.
Does anybody has any experience with Samsung or knows a link where I can find more info?
Thanks!
Google Play is a non exclusive app store. You are free to distribute your app via other channels, such as Amazon App Store, Samsung App Store, emailing apks and even direct downloads from your own site.
Any app that has been written with the Android SDK should work on any device running the supported versions Android (assuming the OEM has a bug free and AOSP based ROM).
Keep in mind though that some devices that have the Samsung App Store may not have Google Play and may not be able to use Google Services like In App billing and licensing.
Be warned with Samsung Apps, they take huge fees, there are many intermediaries (agents, commissionaires). While in Google Play you get 70% of the sales, in Samsung Apps you barely get 30-35%... And you are paid 6 months later.