Search Results

Google runs a static analyzer over the bytecode. This code will never run and will not cause any problem (unless you use the deprecated DoEvents or Msgbox calls).
link: API (unsupported) Warning Issue 1 of 7 Called 2 times during testing API Landroid/os/Message;->flags:I Stack trace #1 StrictMode policy violation:

Hi, the Google Play Pre-launch report for my app shows the following Android Compatibility warnings: We’ve detected that your app is using unsupported APIs. The following APIs are greylisted and Google can’t guarantee that they will work on existing versions of Android. Some may be already be rest
link: I have replaced all Msgbox (not async) / DoEvents from my code. Still I get the same Android Compatibility warnings in the Google Play Pre-launch repo

This is only a warning and you should ignore it. It will do no harm.
link: Hi, I had the same issue. It caused my App to crash on Android 10. After updating B4A to version 10.5 and setting android:targetSdkVersion="29" it wa
link: Hello everyone. I never took a in consideration Google Pre-Launch reports and now while i was looking at them i saw the following error: StrictMode

I see a few posts on here regarding concerns about StrictMode policy violations being reported in pre-launch reports - & in fact I had a bunch in a report for a new app that I released to my internal testing track. Here's a link to the Android Developer documentation regarding StrictMode policy vio

These warnings have nothing to do with the AdMob issue you encountered. You should ignore them. They will do no harm.
link: In attached are errors before (I use AdMob and MsgBox) Ljava/nio/Buffer;->address:J Landroid/content/Context;->bindSer Landroid/os/Message;->flags:I L
link: Hi, This is my first post in forum. I have the same problem like: https://www.b4x.com/android/forum/threads/pre-launch-report-android-compatibility-
link: Looking at the reason (which I assume is a translation to English, because the first sentence doesn't really make sense) I'm guessing you somehow used

After uploading my app I have nineteen compatibility errors. These 4 StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/os/Message;->flags:I StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/os/Message;->recycleUnchecked()V StrictMod

Here is a couple of stack traces from one of the warnings. StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: ;->getAlpnSelectedProtocol() at android.os.StrictMode.lambda$static$1(StrictMode.java:428) at android.os.-$$Lambda$StrictMode$lu9ekkHJ2HMz0jd3F8K8MnhenxQ.accept
link: I have uploaded a APK created with B4A to the Google Play Console. After a short time I receive a pre-launch report with 9 warning identified stating
link: You can ignore these two: StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/os/Message;->flags:I StrictMode policy

Hello community, publishing one of my apps in Play Store I received the warning: StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/os/Message;->recycleUnchecked()V This is something related to the use of "non sdk api". But I didn't use any external api in my
link: Ignore it. It is only reached if you call the deprecated DoEvents or Msgbox keywords. I guess that you should also ignore the conscrypt warning.

An app I am submitting has a series of Strict mode policy warning in the Google Pre-Launch report. 'StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V' The make 'makeOptionalFitsSystemWindows' call shows in their re
link: It will not be a problem and it happens inside Google SDK.

I got a pre-launch report from Google. It contains 10 unsupported API issues and this, about okhttp, is the first one. Could someone show me how to fix it? Can I ignore it? API: ;->getAlpnSelectedProtocol()Stack Trace #1: StrictMode policy violation: android.os.strictmode.NonSdkApiUsedVio

Powered by ColBERT