The app doesn't open

Good afternoon. I have an application, I used to sign the following signature key:
keytool -genkey -v -keystore mykeystore.keystore -alias aliasname -keyalg RSA -validity 999999.

The key was created, but an error occurred at the end:
Warning:The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using “keytool -importkeystore -srckeystore mykeystore.keystore -destkeystore mykeystore.keystore -deststoretype pkcs12”. ( I do not know how to fix it)

Next, the app compiles perfectly, but when you try to install it on your device, it doesn’t open! I thought it was because it’s not in the Play Market, but when I uploaded it there, the error persisted. Maybe something is wrong with the key or with java. I really hope for your help!

What error are you getting in the adb console? Without that there is really nothing to go on.

18:19:43.256 Android build failed (1) after 46 seconds
18:20:35.811 Testing credentials for ‘C:\Games\KeyFor*******.keystore’:
18:20:37.015 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:20:37.015 jar signed.
18:21:29.700 Excluding specified files from build:
18:21:29.700 excluding: LaunchScreen.storyboardc
18:21:29.700 excluding: Icon.png
18:21:29.700 excluding: Icon-*dpi.png
18:21:29.700 excluding: Images.xcassets
18:21:29.700 Android build succeeded in 52 seconds
18:28:14.220 Testing credentials for ‘C:\Games\DCapp.keystore’:
18:28:14.502 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:28:14.502 jarsigner: key associated with dc not a private key
18:28:24.331 Testing credentials for ‘C:\Games\DCapp.keystore’:
18:28:24.616 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:28:24.616 jarsigner: key associated with dc not a private key
18:28:32.529 Testing credentials for ‘C:\Games\DCapp.keystore’:
18:28:32.815 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:28:32.815 jarsigner: key associated with dc not a private key
18:38:47.341 Testing credentials for ‘C:\Games\DC.keystore’:
18:38:48.591 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:38:48.591 jar signed.
18:39:43.422 Excluding specified files from build:
18:39:43.422 excluding: LaunchScreen.storyboardc
18:39:43.422 excluding: Icon.png
18:39:43.422 excluding: Icon-*dpi.png
18:39:43.422 excluding: Images.xcassets
18:39:43.422 Android build succeeded in 55 seconds
18:44:32.598 Testing credentials for ‘C:\Games\DC.keystore’:
18:44:32.892 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:44:32.892 jarsigner: key associated with dcapp not a private key
18:44:38.839 Testing credentials for ‘C:\Games\DC.keystore’:
18:44:39.154 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:44:39.154 jarsigner: key associated with dcapp not a private key
18:44:47.034 Testing credentials for ‘C:\Games\DC.keystore’:
18:44:47.360 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:44:47.360 jarsigner: key associated with dcapp not a private key
18:44:53.715 Testing credentials for ‘C:\Games\DC.keystore’:
18:44:54.042 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:44:54.042 jarsigner: key associated with dcapp not a private key
18:51:08.403 Testing credentials for ‘C:\Games\mykeystore.keystore’:
18:51:09.649 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
18:51:09.649 jar signed.
18:52:02.004 Excluding specified files from build:
18:52:02.004 excluding: LaunchScreen.storyboardc
18:52:02.004 excluding: Icon.png
18:52:02.004 excluding: Icon-*dpi.png
18:52:02.004 excluding: Images.xcassets
18:52:02.004 Android build succeeded in 53 seconds

The fact is that the application compiles successfully. In the debug version, everything starts correctly, but in the release version, there is no startup.

But on the device, you should see an error. The log that you provided is the build process. The warning means nothing. I get that warning about the key all the time. You need the error as the app launches.

I don’t see the error. The app just won’t start. In the debug version, it starts, but in the release version, it does not, it just crashes without starting. Do you have any suggestions as to why this is happening?

I would have a million guesses. You will have an error. Things do not crash without an error. You might have to look at the logs without a filter or filter on the PID of the particular launch.