Android Question When touch the EditText, the program jumped out (crash)

[foretek]

I use an EditText in my APP. First a string is loaded to the EditText.Text, and when the EditText is touched on screen, it pop up a keyboard and works. In the APP, another string is then loaded to the EditText.Text, this time when the EditText is touched, the program is crash. I couldn't catch the cause of the problem. I got some message as below. Can anyone give me a hint what the problem might be? Thanks.

 

[DonManfred]

1. An error in the log is Text. Please post it as TEXT (right click to copy)
2. I don´t see any Projectupload which shows the problem. Hard to help without seeing what you are doing exactly.

 

[Erel]

I've seen such errors when apps use Android 2 theme on new devices. Please post your manifest editors code.

 

[foretek]

Thank you for replies. In the manifest, I tried to add a line of 12 and it didn't fix it.

I collected the whole logs from beginning to run the APP until it crashes as attached.

 

[foretek]

I ran and checked the logs for my previous version of the code before I added the EditText in. The log shows the same "FATAL EXCEPTION" messages in the beginning of the log. Even this code was running ok without crashing. It looks my code has potential defect inheres in it.

 

[DonManfred]

It would help if you upload the project to see it running

 

[foretek]

Hi, DonManFred, I am uploading my early version of the project, which doesn't have the EditText but it shows in Debug Mode the same "FATAL EXCEPTION" messages as in the later version of the code. I am thinking these FATAL EXCEPTION may be the root cause of the problem. Would you please check what goes wrong and how to fix it. Thank you for the help.

 

[DonManfred]

i replaced your incomplete manifest with this one

AddManifestText(
<uses-sdk android:minSdkVersion="5" android:targetSdkVersion="26"/>
<supports-screens android:largeScreens="true"
    android:normalScreens="true"
    android:smallScreens="true"
    android:anyDensity="true"/>)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
CreateResourceFromFile(Macro, Themes.DarkTheme)

and ran your app in debug

i saw a layout with two buttons and a grid but no crash happens

 

[foretek]

Hi, DonManFred, thanks for quick reply. I'll try the manifest soon. Here is the project with EditText and it crashes.

 

[DonManfred]

Start with a NEW Project. Let the manifest like it was.
Adapt your code in there then.

I added the adapted manifest to your second app and it does NOT crash.

 

[klaus]

Here is the project with EditText and it crashes.

Because you haven't changed the manifest !
Attached your project with the new manifest, which works like for DonManfred.

 

[foretek]

Hi, I replaced you new manifest scrips to the existing project, it does NOT crash. Great. But I found that the fix also disabled the AddMenuItem button. Can we bring back the button, which I use it for bluetooth?

Activity.AddMenuItem("Connect", "mnuConnect")
Activity.AddMenuItem("Disconnect", "mnuDisconnect")

 

[klaus]

I don't know, I never use Activity.AddMenuItem.

 

[foretek]

AddMenuItem button is very nice space saving button with icon " ⋮ " at the right corner. Just wanted to make sure if the new version B4A has eliminated the button? If it is, new coding need to be made for the new B4A. I wish it kept that.

 

[klaus]

Just wanted to make sure if the new version B4A has eliminated the button?

I don't know.
Anyway, if this happens it is not due to B4A but to Android.
Google adds in every new version new features and also removes some features.

 

[foretek]

I would think it is more related to my APP. I use the same phone, same version of Android, it shows the button and works fine before the manifest change. Does it make sense?

 

[DonManfred]

Does it make sense?

Yes. The key is Elevation which is applied in Android 5 or 6

 

[foretek]

The phone I am using has Android 8.1.0 on it. The key worked on the phone with the old manifest. The new manifest fixed the crash problem but caused the key loss. I just wanted to know, is it possible for me to use the key again with some new manifest not crashing? It is ok if there is no way to use the key again. I'll change my code.

 

[klaus]

Do you see in the top right corner the three dots?

That's the menu!

 

[foretek]

Hi, Klaus, I found that if the code: "#IncludeTitle: False" is changed to be True, we can see the "Activity ⋮ ". Thank you for bringing it back. But unfortunately the " ⋮ " key will always take a whole new line space on top of the screen instead of shared with system buttons at bottom as it was in old manifest. Is there any way this line can be auto-hide? Otherwise it takes a little too much space for the APP.