Problems with debugging and deploying to emulator.

Question

Problems with debugging and deploying to emulator.

Jesse Knott 691

Hello, I've asked this question in the past, but in a different context.
I am having a bizarre problem with when I try to debug my app. This has only begun since I had updated VisualStudio after a previous hiatus from programming.
In the past I was able to build and deploy to the emulator using the default configuration for my Android project. The project is defined to build a package and to support x86, x86-64, and both of the armeabi's. For some reason now I cannot deploy to the emulator I cannot do so unless I disable the two armeabi's. In the past when I deployed the project to the emulator it would run no matter what options I had selected.

Is this some known issue? Do I need to roll my compiler back to a previous version? Am I experiencing something novel and unique?

Cheers!

JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-17T07:30:30.047+00:00

The project is defined to build a package and to support x86, x86-64, and both of the armeabi's.

Do you mean you can't deploy your app to your emulator when checking all the options of supported architectures? Is there any logs?
Jesse Knott 691 Reputation points

2021-05-17T21:59:30.663+00:00

Correct, If I use an x86 Emulator, but leave all four options checked, it will not deploy, claiming that the architecture is not supported.
I will try to gather some logs a little later today. I will capture the output window, but are there any other log files that I should gather?
JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-18T06:15:39.903+00:00

You can check Getting Diagnostic Information to know how to get Diagnostic Information. But you can try to create a new x86 emulator and try again.
Jesse Knott 691 Reputation points

2021-05-18T07:51:49.697+00:00

Thanks for the link! I'll try to get a log to post soon. I have found that it only seems to happen with Release builds. As it seems for now, the only error indication is this

Severity Code Description Project File Line Suppression State
Error ADB0020: Android ABI mismatch. You are deploying an app supporting 'armeabi-v7a;arm64-v8a' ABIs to an incompatible device of ABI 'x86_64;x86'. You should either create an emulator matching one of your app's ABIs or add 'x86_64' to the list of ABIs your app builds for.

Which is displayed in the Errors tab on the IDE. There is simply a message stating that the deployment failed.
I will try to gather more details soon.

Cheers!
JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-19T09:08:17.4+00:00

You can try to cancel all the selected options of supported architectures and check them again.After that, try to rebuild and deploy your app again.

1 answer

Your answer

JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-17T07:30:30.047+00:00

The project is defined to build a package and to support x86, x86-64, and both of the armeabi's.

Do you mean you can't deploy your app to your emulator when checking all the options of supported architectures? Is there any logs?
Jesse Knott 691 Reputation points

2021-05-17T21:59:30.663+00:00

Correct, If I use an x86 Emulator, but leave all four options checked, it will not deploy, claiming that the architecture is not supported.
I will try to gather some logs a little later today. I will capture the output window, but are there any other log files that I should gather?
JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-18T06:15:39.903+00:00

You can check Getting Diagnostic Information to know how to get Diagnostic Information. But you can try to create a new x86 emulator and try again.
Jesse Knott 691 Reputation points

2021-05-18T07:51:49.697+00:00

Thanks for the link! I'll try to get a log to post soon. I have found that it only seems to happen with Release builds. As it seems for now, the only error indication is this

Severity Code Description Project File Line Suppression State
Error ADB0020: Android ABI mismatch. You are deploying an app supporting 'armeabi-v7a;arm64-v8a' ABIs to an incompatible device of ABI 'x86_64;x86'. You should either create an emulator matching one of your app's ABIs or add 'x86_64' to the list of ABIs your app builds for.

Which is displayed in the Errors tab on the IDE. There is simply a message stating that the deployment failed.
I will try to gather more details soon.

Cheers!
JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-19T09:08:17.4+00:00

You can try to cancel all the selected options of supported architectures and check them again.After that, try to rebuild and deploy your app again.

Answer 1

Jesse Knott 691

I was finally able to get this working.
I had to manually merge the values from an old copy of the project file in gitlab. For some reason it would not accept the changes from changing the settings in the IDE.

After merging the following line by hand it works now for both Debug and Release deployment.

    <AndroidSupportedAbis>armeabi-v7a;x86;x86_64;arm64-v8a</AndroidSupportedAbis>

I cant figure out why the IDE was unable to write the changes to the project file, but no matter how many times I tried using the IDE to make the changes, I could not get the project to deploy a release build until I manually merged the line above.

Cheers!

JessieZhang-MSFT 7,716 Reputation points Microsoft External Staff

2021-05-24T08:38:29.63+00:00

Congrats,could you please mark your reply as answered so that it will help others who have similar problems?

Share via

Problems with debugging and deploying to emulator.

1 answer

Your answer