Search Results

It seems that recompiling with B4A 11 produces a different package signature than B4A V9. This is what packager signing is about - and is as far as my knowledge goes! https://source.android.com/security/apksigning/ I know that B4A v11 changes some things to do with signing. Hopefully Erel might se
link: Signing package file (debug key). (1.35s) ZipAlign file. (0.05s) Installing file to device. (3.56s) Device serial: R52M80P1ZPN Completed
link: Yes, I did. I used WinRAR to unzip them. I inspected the ZIP files and the folders on disk and all subdirectories appear to be properly un-zipped. A
link: Did you install the accompanying SDK Command Tools and Required Resources? e.g follow: https://www.b4x.com/b4a.html section 2 completly and carefully

permission needed: android.permission.REQUEST_DELETE_PACKAGES. i don't believe it's runtime, but check for dangerous permissions in the ide pop-up after you add it to the manifest. easy enough to remedy if it is. (also think about Intent.ACTION_UNINSTALL_PACKAGE if android.intent.action.DELETE do
link: Only had a chance to try it now, can confirm this works when added to the manifest for Android 11: AddPermission(android.permission.REQUEST_DELETE_P
link: I have been using this code in a service to initiate the uninstall of our setup app for many years. The devices we use have been upgraded from Androi

Since the "" is only available since API30, I have taken another approach. This has worked for me (tested with Android 10). There are changes in Android 11 regarding the Packagemanager, that not all apps will be by default visible to the user. However, I don't think this affects system apps Pls con

intent.action.PACKAGE_ADDED, ngp.n(8): Invalidating cached PackageState for b4a.example11 Slow dispatch took 138ms main h=android.app.ActivityThread$H c=android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA@78f05fb m=0 Slow delivery took 287ms main h=android.app.Activ

Not long ago Don provided example Provider Requester Activity based communication via Intents. Although that Activity version had some hints in it for Service based version, it took several additional steps to get it working (Service Intent must be explicit, which may reflect more on my knowledge l

(Je pensais que l'erreur de commande introuvable s'était peut-être produite parce que j'avais modifié le code du packager B4JPackager11. I just realized that B4JPackager11 is not useful in my example. ) The problem I want to solve is command not found
link: You don't need to use the Standalone Packager. For production, you just need to compile the server in Release mode. jRDC2 is a server app (non-UI) s
link: Matcher2($"^JavaFX-Application-Class:\s+(.*)\.main$"$, Regex.MULTILINE, s) m.Find ' PackageName = m.Group(1) PackageName = "b4j.example"
link: I don't understand anything from this post. Sorry. How is the packager related to the command not found error?

I can package any B4j project and the resulting .exe runs perfectly. However, when I have a project that uses sqlite, the resulting packaged .exe simply does nothing. Stepping through the code reveals that the problem is related to the ExecQuery statement. Here is the Project Attributes section: #R

): 'Input: Optionally, in versions of Android prior to 11, the Intent's data URI can specify the application 'package name to directly invoke the management GUI specific to the package name. For example "package:com.my.app". 'Notice the "prior to 11" 'WARNING: Below w

If possible I would ask @Erel to provide the complete new JDK package when supported. As it was done with 11 and 14. Thanks
link: There are no issues with the current OpenJDK 11 and OkHttpUtils2. The problem was somewhere else.
link: I've been using OpenJDK 14 + OpenJFX 14 from Erels beta release post for a couple of years now for all my B4X projects, it works perfect. My wish is

Erel, definately using SLC V1.11 for building Android Libs. Have just downloaded and extracted it again to make sure I am using the right one. This is the complete error - it builds the Jar successfully but fails to create the XML. Is it maybe because I am using Java 11? Starting step: Compiling Ja

Powered by ColBERT