Just noticed that Google's Pre-Launch Report for my app has raised a "Usage of non SDK interfaces" issue when testing against an Android 9 device.
The logcat has recorded many instances of the violation with the following being an example chosen at random.
Would I be correct in assuming that this issue is due to the code that B4A generates rather than what I have written? And hence it will be fixed in a future version of B4A?
The logcat has recorded many instances of the violation with the following being an example chosen at random.
B4X:
37315 09-27 10:53:49.854: D/StrictMode(12541): StrictMode policy violation: android.os.strictmode.NonSdkApiUsedViolation: Landroid/view/WindowManagerGlobal;->mViews:Ljava/util/ArrayList;
37316 09-27 10:53:49.854: D/StrictMode(12541): at android.os.StrictMode.lambda$static$1(StrictMode.java:428)
37317 09-27 10:53:49.854: D/StrictMode(12541): at android.os.-$$Lambda$StrictMode$lu9ekkHJ2HMz0jd3F8K8MnhenxQ.accept(Unknown Source:2)
37318 09-27 10:53:49.854: D/StrictMode(12541): at java.lang.Class.getDeclaredField(Native Method)
37319 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.base.RootsOracle.a(RootsOracle.java:13)
37320 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.base.RootViewPicker$RootResultFetcher.a(RootViewPicker.java:5)
37321 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.base.RootViewPicker.a(RootViewPicker.java:37)
37322 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.ViewInteractionModule_ProvideRootViewFactory.get(ViewInteractionModule_ProvideRootViewFactory.java:10)
37323 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.base.ViewFinderImpl.a(ViewFinderImpl.java:10)
37324 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.ViewInteraction.a(ViewInteraction.java:58)
37325 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.ViewInteraction.a(ViewInteraction.java:94)
37326 09-27 10:53:49.854: D/StrictMode(12541): at androidx.test.espresso.ViewInteraction$1.call(ViewInteraction.java:3)
37327 09-27 10:53:49.854: D/StrictMode(12541): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
37328 09-27 10:53:49.854: D/StrictMode(12541): at android.os.Handler.handleCallback(Handler.java:873)
37329 09-27 10:53:49.854: D/StrictMode(12541): at android.os.Handler.dispatchMessage(Handler.java:99)
37330 09-27 10:53:49.854: D/StrictMode(12541): at android.os.Looper.loop(Looper.java:193)
37331 09-27 10:53:49.854: D/StrictMode(12541): at android.app.ActivityThread.main(ActivityThread.java:6669)
37332 09-27 10:53:49.854: D/StrictMode(12541): at java.lang.reflect.Method.invoke(Native Method)
37333 09-27 10:53:49.854: D/StrictMode(12541): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
37334 09-27 10:53:49.854: D/StrictMode(12541): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Would I be correct in assuming that this issue is due to the code that B4A generates rather than what I have written? And hence it will be fixed in a future version of B4A?