API Level 33

[Nii Darko Darkoh]

Hi DS,
When publishing my app to PS, I recieved the following warning:
"Your highest non-compliant target API level is Android 12 (API level 31).

To ensure that you can continue to make updates to your app you must:

1. Update your app to target Android 13 (API level 33) or higher.
2. Publish a new version of your app to production. Before you do this, you can test your app using internal, closed, or open testing." 

What's the solution please?
Regards,
Nii

[Dave]

https://groups.google.com/g/droidscriptpremium/c/yP3g_E18324/m/ML_RqTKkAwAJ

[Alan Hendry]

HI,

If you can't read the Premium Groups it says

you can ask for an extension.   Just choose the option that says something like "I have to make lots of changes..."

That should give you another couple of months to sort it out.   

We will be releasing a new version of DS soon that can build for the latest target API level

Regards, ah

[Nii Darko Darkoh]

Hi Dave,
when I clicked on the link I was told I have no access meanwhile I am on Premium too.
What do you advice please?

-Nii

[Eduardo Paredes]

Today I uploaded a new version of my APP to the Play Store, and it does not allow me to publish it, as it is not oriented to targetSdkVersion 33.

I need a solution.

Dave, when can we compile with targetSdkVersion 33?

I look forward to your news.
Thank you
Eduardo Paredes

[Eduardo Paredes]

Hi Dave,

When can we compile with targetSdkVersion 33?

I look forward to your news.
Thank you
Eduardo Paredes

[Nii Darko Darkoh]

Hi Team,
What is the status with this issue please?
-Reid

[Dave]

Hi this question needs to be asked in the Premium forum as APKBuilder is a premium feature.

[Nii Darko Darkoh]

Please share the Premium link with me.
Thanks.
--Nii

[Alan Hendry]

HI,

It's in Google Groups

If you are Premium and haven't got access then you can ask for it here

Regards, ah

[Eduardo Paredes]

Hi Dave,

I urgently need to be able to publish my application for Android 13, in the Play Store.

Is there already a solution for this need?

When will it be available?

Please tell us something.


Kind regards.
Eduardo Paredes

[Jumar]

Hi

I don't know if this still works today, but before whenever I have the same issue as this, I will just create a build.json file and paste the code below.

{
    "manifest":
    {
        "minSdkVersion": 28,
        "targetSdkVersion": 33
    }
}

Just modify those values as needed.

Regards

Jumar

[Dimas]

first all go to playstore and download the apk to aab coverter

in your droid script app create a build.json file like a frend mentioned above

don't compile in abb file, compile in apk file aab file not working

go to the apk to aab converter convert your apk file to aab

before you compile it you must select the user.keystore to to asign the the aab file 

it locate in aab droid script files

[Eduardo Paredes]

I've been working with the BUILD.JSON file for a while now, where I added "targetSdkVersion": 33, but it's not working. When I upload my APK to Google Play Developer, it only recognizes the APK as targetSdkVersion=31, ignoring the contents of the build.json.

As a result, the app cannot be published.

[Eduardo Paredes]

I've tried what you suggested, and it's not working for me.

El lunes, 18 de septiembre de 2023 a las 2:45:08 UTC+2, ddd29...@gmail.com escribió:

[Alan Hendry]

HI,

Pretty sure PlayStore requires new apps to be ABB 

(I suspect that if your app was uploaded as APK quite a while ago then you can upload new versions of the APK).

Not sure if build.json filename is case sensitive (mine are lower case, and at top level inside the project/app).

Worth checking the format of your build.json (just in case).

PlayStore sent me an email that my apps weren't Android 13 compatible, but the console let me delay the cut-off date.

Regards, ah

[Dave]

A new beta version of DS will be released tonight or tomorrow that supports targeting API 33 

[Eduardo Paredes]

Thanks Dave, I'm waiting for it.

[Eduardo Paredes]

Hi Dave.
Is the new beta version of Droidscript compatible with API 33 already available?

Thanks

[Dave]

Yep, I invited you to the beta group. 

[Oskar Sjögren]

I seems to have the same problem as the guys above. Can you please add me to the beta group too?

[Eduardo Paredes]

Hi Dave,

I have finally generated the APK of my APP again, for Android 13. And now when I run it, the message "Error Missign Permissions" always appears. When I accept the message the application closes.
My APP has location, camera and microphone permissions activated, and on Android 12, it works correctly.

Please, I need an urgent solution.

Thank you.
Eduardo

[Dave]

Did you use the DS beta from here and use the APKBuilder from here too?

http://androidscript.org/beta/DroidScript_263b1/

Note: remove the .zip extension from the APKBuilder.ppk if your phone adds it.

[Jumar]

Also, did you add

_AddPermissions("Location,Camera,Microphone");

At the top of your code?

[Dave]

Android 13 requires the latest beta - 

http://androidscript.org/beta/DroidScript_264b1/

[Oarabile Koore]

Hey, Dave on another note, I've been trying to contact the DS team about CloudStore on mail, I need help please. 

[Eduardo Paredes]

Hi Dave.
I have generated my APK with the latest beta version available 2.64b1. And my APP still has problems with missing permissions on Android 13.

Please, I need an URGENT solution to this problem, I have been waiting for more than a month.

You can help?
Please, tell me something.

Thank you.
E. Paredes

[Dave]

@EPeredes:  This should have been fixed in 2.64b1 of the APKBuilder..... are you sure you installed the latest APKBuilder properly?

[Eduardo Paredes]

Yes, Drodidscript IDE and APKBuilder, we are in version 2.64b1.

And Build.json file have the next content

{
  "manifest": {
    "targetSdkVersion": 33,
    "requestLegacyExternalStorage": "true",
    "preserveLegacyExternalStorage": "true"
  }
}

I go to try, whitout Build.json file.

[Oarabile Koore]

Im expiriencing the same problem i figured a way out by setting autoPermissions to false and asking for them independently.

Also, notifications dont work, i think its because of the new notification permissions on android 13

[Jumar]

The file is build.json, not Build.json. Try this one.

[Oarabile Koore]

It still doesnt work, try running the material ui (premium demo) it will give a missing permissions alert:

download MUI icons spk from the droidstore, you will get the same error, Its not just isolated to materiall you, even some of droidscripts samples give out that message, try using notifications sample they dont work, not because i didnt give droidscript notification permissions it didnt ask for them. I did this to get rid of the message temporarily: {
    "manifest":
    {
        "minSdkVersion": 26,
        "targetSdkVersion": 33,
        "debuggable": false,
        "homeScreen": false,
        "urlHost": "*",
        "urlScheme": "http,https"
    },
    "autoPermissions": false
}

[Dave]

Try this version - 

http://androidscript.org/beta/DroidScript_264b2/

[Oarabile Koore]

Thanks, it works . 

[Jesse James]

It works target api 33 is met but reads me this error now

Error

You can't rollout this release because it doesn't allow any existing users to upgrade to the newly added app bundles.

Read online have to change Version Code in gradle build but im not sure how in Droidscript..my app build now is 2.1 instead of 1.09

[FrickelPit]

Refer to my post https://groups.google.com/g/droidscriptpremium/c/Xc6p_R47q1w
and give it version number 2.01.

Regards Peter 

[Jesse James]

Okay thank you, I cannot see your post yet as emailed support about re-joining premium forum still waiting, would be nice if didnt have to do that, I do not keep subscription always or would be losing money not making money but if things pickup would gladly keep subscription

[Jesse James]

Okay so I think I followed your advice and instead of putting 2.1 I put 21 seen as that was the only problem Play Console warned me of, and than now it just simply says cant upload bundle even though that was litteraly the only error now doesnt tell me whats wrong. I have project put years into and am thinking of just switching it over to Unity or something and re-coding it, Droidscript is awesome when it works but I cant be bothered doing this anymore and not making money and having to waste extra time its just so frusterating

On Saturday, November 4, 2023 at 3:44:21 AM UTC-5 peter.s...@gmail.com wrote:

[Dave]

You should make your app version 2.10 not 21

Also... be aware that Google Play sometimes says 'Can't upload' even when the app has successfully uploaded.  I've seen this when the network is running slow.  If you refresh your browser you might see that you have already uploaded the 2.10 version (or 21.00 version if you used 21).  

Note: You cannot upload the same version twice, so you will need to increment your version number by 0.01 the next time you update.

[FrickelPit]

@Dave Version 2.10 will result in a version-code of 21 in Android Manifest, which is lower than version-code 109 (result of Jesse's previous version 1.09). So it will be rejected by Google. My earlier testing showed me, that trailing zeroes are ignored by DS when building the version-code for Android Manifest in AAB. If i'm wrong, i beg your pardon, but until now you answered none of my posts regarding this issue.
Regards Peter

[Jesse James]

Okay thank you, it worked now after clearing all data and making sure everything was closed, and only loading Google Play page to upload, and changing version to 21.01

[Dave]

The manifest contains two entries - a text version and an integer version code.  If you use a version number of 2.10 (or 2.1) in DS, it should result in a manifest versions of "2.1" and 210 respectively.... are you saying that APKs and AAB generation behaves differently?   Does the language make a difference (ie. comma instead of period in decimals?

Note: DS takes the text version number and multiplies it by 100 to get the integer version.

[Dave]

OK, looking at the AAB building code, it looks like the x100 is not happening for AAB's..... that would explain why AAB's have mis-matched version pairs in AAB's but not APKs when using decimal version nums.  I'll fix that right now,

[Dave]

@succedinglights:  Sorry for all your trouble.    Next time you release that app you can release it as 21.02 

I discovered that the AAB builder was just stripping out the commas and decimals points to generate a version number from a version string (not multiplying by 100).  The version string was converted to a decimal and back to a string which means 2.10 --> 2.1 --> 21, however 2.11 --> 2.11 --> 211 which works. 

So in the current release, you need to avoid trailing zeros as Peter says.  

Some confusion was caused by it working ok in APKs.

[FrickelPit]

Wow, I'm really glad that this issue will be fixed now. But please keep my post https://groups.google.com/g/droidscriptbeta/c/IMLZoHEr9Cs
from 11. and 12. october in mind, where i sent 2 screenshots showing a version name with decimal point generated with Android language setting 'English' and version name with decimal comma generated with Android language setting 'Deutsch'

I think, DS will look much more professional, if you let the user input different fields for version name and version code when generating APKs and AABs. Another advantage would be the opportunity to specify version names like 1.3.1 with major, minor version and build number. 

Regards Peter