Search Results

ADB installation allows downgrading apps, based on the #VersionCode value. Comment link to go to layout: 'main page layout - ide://goto?Layout=MainPage Updated internal libraries: XUI v2.3, RuntimePermissions v1.2, Core v12.5, SimpleMediaManager v1.13, BCTextEngine v1.95, B4XFormatter v1.04, XUI V
link: Thanks @Erel for the new version! Another contribution to the development was made by PayPal: 1GX78908H82540712
link: PERFECT!! (compiled with out problems) B4A Versión: 12.50 Parseando código. (0.44s) Java Versión: 11 Building folders structure. (0.80s) C

The one that controls your app's availability for previous android versions is minSdkVersion, so as long as you don't change that you're good (and also are careful about trying to use new APIs in older android versions).
link: If you don’t publish to PlayStore put whatever you want. You will be forced to target 30 by August 2021 if you publish to PlayStore.
link: Hi all. I have 2 questions. 1. Do I need to change my from targetSdkVersion=29 to targetSdkVersion=30 now? 2. Is there any previous Android versi

Hi, All I have found that if targetSdkVersion is "33" - no is shown in the app settings. And no request system dialog and Waiting For permission request is always with False result. It's in B4xPages structure app, tested under Android 13 device and 2 emulators (Android 10). B4A v.12.5, rp lib v.1.
link: The external storage permission cannot be used since at least targetSdkVersion=31. Other methods are available: https://www.b4x.-let-the-user-select-
link: I'm making a picture gallery app using SimpleMediaManager and any local available photos. Without this permission no files gotten.
link: Starting from targetSdkVersion=29 (Android 10) you cannot directly access the external storage. Maybe you previously used requestLegacyExternalStorage

The Workaround is exactly on top of what you quoted above... SetApplicationAttribute(android:requestLegacyExternalStorage, true) https://www.b4x.-jar-targetsdkversion-minsdkversion.87610/
link: I read Does that mean in the future we can't use File.DirRootExternal? Will there be a workaround just like the manifest for targetSdkVersion=29?
link: The way i read it "will not work with targetSdkVersion=30" and "Avoid using File.DirRootExternal" Why avoid using File.DirRootExternal? I have bee

No. targetSdkVersion can be 29 for now. Switch to B4A 10.7 (currently beta) and it will work.

I see it now. Investigating!
link: Hi, All If to set the latest targetSdkVersion="33" - GNSS lib again gives the error: at GNSS1.Start(0, 0). If targetSdkVersion="30" - all works OK.
link: Check the paragraph in bold at the end of the first post. https://www.b4x.-library-an-updated-gps-library.109110/#content

Hola Gonzalo: El targetSdkVersion es un número entero que designa el nivel de API que la aplicación apunta. Si no se establece, el valor predeterminado es igual al de minSdkVersion. Para entendernos, el targetSdkVersion hace referencia a la API con la cual vas a compilar tu aplicación, los disposi
link: Si en el manifiesto pongo targetSdkVersion="23", significa que las personas que tengan versiones superiores no podran ver mi app en Play Store?

Example was updated. targetSdkVersion is set to 29 and it is based on B4XPages, which makes everything simpler. Note that usage of Wait For with the completed events.

Setting the targetSdkVersion to 23 means that you are using runtime permissions: Runtime Permissions (Android 6.0+ Permissions) The simple solution is to use RuntimePermissions.GetSafeDirDefaultExternal("") instead of File.DirRootExternal.

The targetSdkVersion is set to 19 so runtime permissions are not needed.

Powered by ColBERT