fredo Well-Known Member Licensed User Longtime User Jul 14, 2018 #1 I put this here so it might be helpful for someone else. While testing an app via the Firebase "Test Lab" there where this strange errormessage only on certain devices: "Native crash of ..." regadless of the API. Due to hints from here and from SO I started commenting out suspicious lines of code and finally came to this: https://stackoverflow.com/questions...error-in-application?answertab=active#tab-top Click to expand... Since B4A itself is a very clean constructed environment the problem could only lie in one of the comfortable side entrances. B4A's Quick search of "jo.RunMethod(" finally lead to this line, which was commented out: B4X: jo.RunMethod("setStateListAnimator", ... Subsequent test labs with several combinations of devices, manufacturers and API could not cause the error again. So, what remains for me is the realization that odd effects might be to be found first in the code areas that are not under the direct control of B4A.
I put this here so it might be helpful for someone else. While testing an app via the Firebase "Test Lab" there where this strange errormessage only on certain devices: "Native crash of ..." regadless of the API. Due to hints from here and from SO I started commenting out suspicious lines of code and finally came to this: https://stackoverflow.com/questions...error-in-application?answertab=active#tab-top Click to expand... Since B4A itself is a very clean constructed environment the problem could only lie in one of the comfortable side entrances. B4A's Quick search of "jo.RunMethod(" finally lead to this line, which was commented out: B4X: jo.RunMethod("setStateListAnimator", ... Subsequent test labs with several combinations of devices, manufacturers and API could not cause the error again. So, what remains for me is the realization that odd effects might be to be found first in the code areas that are not under the direct control of B4A.
Erel B4X founder Staff member Licensed User Longtime User Jul 15, 2018 #2 JavaObject calls are not "native" / jni calls. Upvote 0