-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Gallery][Catalyst] Cannot run the application #17318
Comments
This is a known issue xamarin/xamarin-macios#14686, though supposed to have been fixed in net8, but obviously not. |
Also a duplicate of #15319 |
@jeromelaban for the two issues (xamarin/xamarin-macios/issues/14686 and #15319) you mentioned:
As you mentioned, the issue is supposed to be fixed with net8, but it also seems to me that the report is a bit different compared to the previous ones shared in xamarin/xamarin-macios#14686 and xamarin/xamarin-macios#16230 with "PC register does not match crashing frame (0x0 vs 0x105A29A78)", I'm not sure if this difference is important here: (cc @spouliot) |
The last message is likely not relevant, the security policy one is the actual error. |
I can run the Uno.Gallery on my arm64 Mac.
But the crash report mention it's the When I build/run for
|
My stack trace from my crash points to several frames that suggest the interpreter is active. If I install the app from TestFlight then I get the same, original stack trace. So they are likely different issues... @jeromelaban I think we should publish a fat (x64 + arm64) binary of the gallery app since this is what most people are likely to do when publishing (and is the scenario we should test foremost). This might (or not) fix the issue - even if that's not the main reason to do it. |
I created a new issue for the 2nd (runtime) crash. |
As far as I can tell, we're building catalyst using It's surprising that we're seeing this. |
Indeed. Double-checking shows that both arch are present in the main binary
but the crash mention
so something is not right. |
Locally, building Release and fat, it's the arm64 version that launch (by default) when starting the app (using the IDE or Finder does not change that). Unclear why the TestFlight binary behaves differently ?!? |
We could try removing the x64 variant and see if it helps. |
Docs update: #17815 |
@jhanvi03 can you re-test Gallery Canary Catalyst using TestFlight to see if you are now able to install the application please |
QA Verified - Able to download and open Gallery Canary from TestFlight. Screen.Recording.2024-08-16.at.5.42.06.PM.mov |
Current behavior
Using TestFlight to install the Gallery canary application, we are not able to run the application for Catalyst.
Here is the full report:
Expected behavior
Being able to install and run the Gallery canary application for Catalyst.
How to reproduce it (as minimally and precisely as possible)
Use Testflight and try to install and run the Gallery canary application for Catalyst
Workaround
N/A
Works on UWP/WinUI
Yes
Environment
No response
NuGet package version(s)
N/A
Affected platforms
Mac Catalyst
IDE
No response
IDE version
N/A
Relevant plugins
N/A
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: