LiveCode Forums

Hi, sphere Sorry, It's my apologies for made everyone busy on this precious weekend. I made a mistake managing the version name after I failed the first upload. Now the uploading process is working fine as expected. I learned very important stuff from you. Thank you for your time and effort. Have a ...

I uploaded the 32bit apk first. I also tested again with the new app creation but I got the same result.

Yes, I used LC 9.5.0 (stable) 4 APK's (1x ARMv7, 1x ARMv8_64, 1x X86, 1x X86_64). Set Minimum Android Version to 4.2 Is working fine with you? Try to create a new app and upload a test APK if you have time. I had no problem publishing the app a few months ago but this time it blocks uploads. I've se...

The error was shown for the armv7 app that is made for the 32bit system. It's possible that new guidelines applied for new apps while current apps able to upload without App Bundle.

Again :cry: Unfortunately, uploading multiple APKs is not allowed anymore. I created 4 separate APKs for each system structure; armv7, arm64, x86, x86_64. and I uploaded the first APK but I got 1 error message & 1 warning sign. There is no next button available but only go back or discard buttons ap...

Fantastic! That's very detailed explanation. I really appreciate your help!

Have a great weekend!

Great advice! I have two questions to confirm that I got it right: So armv7 will be 1 Arm64 will be 2 The x86s in one build will be 3 1. Do three APKs have an identical Identifier, Version name but different version code in the standalone settings? 2. Do they have the same app URL? (of course they w...

Hi, sphere I read the last sentence but it can't go further anymore. The button is disabled and there is no way to publish. It seems like it's mandatory now to use it if an app accommodates multiple architectures. I set to build for armv7 and arm64 in the standalone settings. I was advised by the su...

Now, Without using the App Bundle feature, you can't even publish a new app to Google Play. I got the warning message below during the uploading process. The "Next" button is disabled except for an optimized apk. It seems that there are no other choices available. I hope this issue get fixed ASAP.

Making the stack size (width, height) smaller solved the issue. I think that the stack size was too large.

Cheers,

Hello, I made a standalone that dynamically resizes its width and height for tablet screens but the developer console indicates that the .apk file should include custom drawable assets for tablet screens. I got the alert: "Your APK should include custom drawables assets for common tablet screen dens...

No, I am not surprised but I am disappointed with how it performs because the HD screen is normal these days. (1920x1080 or Pixel density of over 4~500 ppi) Let alone Samsung galaxy S10, LG thinQ, Google Pixel, Huawei, Xiaomi, you name it. all mainstream devices have HD screens. App should not under...

Performance (such as scrolling, move, show and hide of images), slows down on Android device with higher screen pixel density. I found that it's slower with image quality set to "best" so I set the image quality to "good". Both Hardware Accelerated and acceleratedRendering set to true in the stack. ...

Thanks guys,

I have reported it a bug to the quality control center.

https://quality.livecode.com/show_bug.cgi?id=22394

Cheers,

Louis

Hi bogs, FourthWorld,

I tested by setting all colors black in the inspector, but the color of the navigation bar does not change. Any walkaround with manifest file?