[android] unknown opcode name for 400, only workaround is UseInterpreter=true
#76192
Comments
|
Does dotnet/maui#9627 have any information that might help you? |
|
Hi @peter-chapman. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
|
That didn't fix it for us. |
|
I have the same issue on my Pax A920 Pro. I've attached the adb log. In the logs I can see "unknown opcode name for 400"; is this possibly related to this unreseolved bug? dotnet/android#6865 |
|
@jonathanpeppers is this supported? |
|
@iain-mcandrew does the app run on this device in any configuration? The crash says The suggestion was to try turning off hot reload / |
|
@jonathanpeppers The app launches and runs fine on this device if the project Configuration is the default "Debug"; creating a project configuration with a differnt name causes the issue. Disabling hot reload and fast deployment does not resolve the issue. |
|
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
|
@jonathanpeppers |
|
So both Can you build the project with Then share these |
|
@jonathanpeppers Here are the requested logs. I had to add ".txt" to the end to upload them here. |
|
One difference between the What if you enable it for every configuration except <PropertyGroup Condition=" '$(Configuration)' != 'Release' ">
<UseInterpreter>true</UseInterpreter>
</PropertyGroup>Does that solve anything? |
|
Setting UseInterpreter to true does seem to fix the Debug.Pax build! |
|
@iain-mcandrew does This will AOT the entire app, instead of using Profiled AOT (the default). It might be there is an issue with the JIT on a specific device? This is a "PAX A920 Pro POS unit"? |
|
Unfortunately, I still get the opcode error. Correct we're using a Pax A920 Pro https://www.paxtechnology.com/a920pro |
|
@grendello any idea what would cause an app on a specific device to crash with: @iain-mcandrew does even a |
|
Stack trace from the log file is very weird: It's impossible to say what leads to the abort, but we think it's happening in this function (I think it might be line 86, since that would call the |
|
I believe the above app crashes even in Debug mode if If it still happens with a |
|
Hi @peter-chapman. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
|
A |
|
Looking at the existing bug, mentioned previously dotnet/android#6865, the user experienced |
unknown opcode name for 400, only workaround is UseInterpreter=true
|
Moving this one to dotnet/runtime. |
|
Tagging subscribers to this area: @dotnet/area-extensions-configuration Issue DetailsDescriptionChanging the name of the configuration causes MAUI apps to crash a few seconds into execution on Android. Steps to ReproduceThis can be recreated by creating a fresh MAUI app and renaming the Debug configuration e.g. Debug.Pax Version with bug6.0.486 (current) Last version that worked wellUnknown/Other Affected platformsAndroid Affected platform versions8.1 Did you find any workaround?No Relevant log outputNo response
|
|
Is there anything we can do to help with this? This is critical to our business so we are happy to support in anyway we can and can provide a device to assist if that would help. |
|
Could we get a stack trace with symbols ? I remember the properties |
|
|
|
@BrzVlad Here's the binlog for a |
|
@iain-mcandrew I was interested in seeing the stacktrace of the crash. So the device logs. |
|
@BrzVlad Logcat of the crash when opening the app. |
|
@grendello @jonathanpeppers Any idea why there are still no symbols in the stack trace ? |
|
I built it again with |
|
Normally the way I get symbols is... Find the path to the (I found this in the Get the symbols: (you might need admin prompt or copy these files somewhere else instead) Use ndk-stack to symbolicate the crash log: But since the crash doesn't say it's inside |
|
@BrzVlad Android ignores symbols most of the time, for some reason. What @jonathanpeppers suggest above is a way to do it. I also often just run @iain-mcandrew could you attach |
|
Also, sometimes running |
|
This is the .so file from the path @jonathanpeppers mentioned. |
|
Here is the result of running |
|
doesn't look like libmonosgen was uploaded. |
|
Not sure why that failed. Hopefully this works: |
|
@iain-mcandrew I have an idea about a potential fix. I would like to get you to try out a custom build of mono. Could we move this discussion somewhere else ? You could reach me on dotnet evolution discord server (I'm Brz_Vlad#8554 there) |
|
Request apk |
Description
My app crashes on a
Pax A920 Prowith:Steps to Reproduce
This can be recreated by creating a fresh MAUI app and renaming the Debug configuration e.g.
Debug.Pax
Version with bug
6.0.486 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
8.1
Did you find any workaround?
No
Relevant log output
See: #76192 (comment)
The text was updated successfully, but these errors were encountered: