I finished a game on the unity game engine and I have an in app purchase button, I tried to upload my .abb file to the play store it said that my API needs to be >= 29, I got back to unity and edited my minimum API and uploaded the file for the internal test to test my IAP button. but the problem is my testing device API is 28 !! I tried Android Studio emulator and it did not work since the emulators have x86 the cpu
how can I install the app from the store to test the IAP button??
and why does google forces the API 29+, that will make me lose many of my users!
how some games are still getting published and compatible with lower API? I installed a game that is published on Jan 5, 2021, on my API 28 device and it works
You have mistaken the target API level with the minimum API level.
You can set the minimum API level to as low as you want.
You need to set the target API level to 29 or higher.
Related
EasyAR. Unity. Problem with publishing. Family Policy
Does Unity version of EasyAR send any of this data to server?
SIM Serial
Build Serial
BSSID
MAC
SSID
IMEI and /or IMSI
We don't have any ads in app, we've remove all libraries corresponded to ad, we've removed all analitics, we've removed firebase from project. Specially we do not send any data to remote server. The only reason may be side modules (EasyAR) that we use in project. Is there any way to find out what module is transmitting this information and how we can turn off the transmission of this information
Here`s email from Google
During review, we found that your app violates the Families Policy Requirements. We’ve identified that Your app or an SDK in your app (App Bundle: 12) transmits identifier(s) from children or unknown users that do not comply with our Families Policy. These identifiers may include but are not limited to Build Serial Number.
The problem is Easy Ar, when sending the bundle id to check the license this error is generated.
I fixed it by switching to the free version of vuforia.
we are having the same issue. our game was published before 2 year ago with easy AR all working fine. but google rejectd this app before a month and mail say that.
Apps targeting children should not transmit the following from children or users of unknown age: SIM Serial,Build Serial,BSSID,MAC,SSID,IMEI and /or IMSI.
we are using unity in-app purchase, but many of our other game use unity inapp but that doesn't have any issue. this might because of easy AR. we are using older version of easyar
Result of Charls proxy see this image
I want to publish my own android game in google play and its my first time trying it with unity I have a background publishing a game with android studio.
I created a new version in the google play console, and inserted the App Bundle and all the pics and the info needed. I sent it for google play to check, and after a few days google approved the version. But when I wanted to downloaded the app from my phone it says: "your device is not compatible with that version". I looked a bit on the intenet, and I think that the problem is that the min API level is too high; 19. With that, I haven't find anyone that showed how to lower it.19 is the lowest API level here.
The app targeted SDK level is 30 (android 11), as google play asked.
Can someone help me with that? Or if you have any other idea how to fix this problem, pleas write it down here.
Thank you!
API Level 18 is from July 9, 2012 .... I think after over 9 years you can kind of stop the support ;)
And that is exactly what hapened
From Meet Google Play's target API level requirement
New apps and app updates must target Android 10 (API level 29) or higher
and
Starting in August 2021, new apps will need to:
Target API level 30 (Android 11) or above and adjust for behavioral changes;
and
Starting in November 2021, app updates will be required to target API level 30 or above and adjust for behavioral changes in Android 11.
so you definitely have to target API level 30 except your app already existed and it is only an update. Then it still needs to be at least 29.
The min version can / is recommended to be kept at the lowest that your app supports (depends on your implementations etc). So if your app supports API level 19 you should keep this as the minimum version.
However, the error sounds more like your test device is using some older API level Android and you should probably use a newer one.
Application is removed playstore by Google Protect.
Every release the version code from Huawei App Gallery is always higher than the version code in Play Store.
The new release version code in the Play Store will higher than the previous release version code in both Play Store and App Gallery.
But the rolling out percentage between the two stores is different. Not sure it would affect
Please help with another quick question. What will happen to App Gallery auto-update if we release the app in Huawei App Store with a different Keystore than the release in Google Play Store?
For the overwriting of each other from AppGallery and Google Play store problem, the root cause is the apps are using the same package name and the same signing key in conjunction with auto-update from both stores. When there is a higher version available from either store, the Android system would recognize it, download and update the app, which would cause overwrite.
The answer is actually in the second question. Using a new keystore for AppGallery would make the app different from the app from GPS from Android system point of view. Please use a new keystore for AG release, there will not be any overwritten problem once this update. Remember to update the SHA256 signature in AG for the new release.
This is a message displayed on Google Protect. We could not restrict the play protect. You can disable Google Protect on your phone manually.
In addition, Google Protect is a black-box detection, which is claimed to be an intelligent detection and may display a message for all apps that are not downloaded by Google Play.
Based on the warning message, this message comes in "Backdoor" category(refer below link).
https://developers.google.com/android/play-protect/warning-strings
Also you can refer the below link
https://developers.google.com/android/play-protect/client-protections#developer-appeal
So you can contact google support team regarding this.
I have submitted a Tizen smart-TV application to the Samsung store, and during the testing process they found that it doesn't start when installed in 2015 devices (it works in modern TVs).
The application was developed in Tizen Studio with TV SDK 4.0, and the minimum compatible platform version is set in the config.xml to Tizen 2.3 (both values apparently compliant with this compatibility table).
Samsung's feedback is the same for 15TV_STANDARD1, 15TV_STANDARD2, and 15TV_PREMIUM model groups: "Blank screen on launching the app."
Any clue about what can be happening with those TV models? Is there any feature that could be causing the crash?
Without more information is difficult to know what may cause the problem with 2015 TVs.
Your best option would be to debug your application on a 2015 model, although I understand this can be difficult.
One thing you can do is to check the Web Engine Specifications and see the differences between the working and non-working models.
Blank screen most likely just means, that your application died somewhere during the initialization.
Did you by any chance use the getDuid() API during initial application initialization? I has some trouble with that if the display has never been connected to the web, so it threw an exception on that call.
Otherwise, assuming the profile is indeed 2.3, then it should work.
I've been a Java developer for 6 years, but this is my first foray into Android, and it's not going well.
I've set up a simple example app which uses google maps api v2 - it's just a single page: I copied it from one of the many helpful sites on this topic.
I then discovered that I can't run it in an emulator since it uses the google maps api v2, which requires google play. So I bought a device (HTC Desire).
Now the device doesn't show up in the eclipse run configuration. It shows up with ./adb devices just fine.
I thought maybe this was because the device is on Android 2.2, and my app has minimum OS level of 4.2. So I tried to upgrade, but I couldn't work out how. In the software / update section on the phone it just says 'no updates available'. Can this be right?
Ok so assuming I can't upgrade the OS (in which case the phone is now useless), I modified the project so the minSdkVersion is now 8. But now my project won't build!
Errors include 'No resource identifier found for attribute 'showAsAction' in package 'android'' - what does that even mean?
And to cap it all the device is now doing the 'buzzing 7 times instead of booting' thing. I can access some menu called HBOOT, and selecting RECOVERY just reboots the machine, which fails.
So now I've spent £50 and several hours, and I haven't even got as far as hello world - just a bricked phone.
What am I doing wrong? Can Android dev really be this hard?