This repository has been archived by the owner on May 1, 2024. It is now read-only.
iOS crash, Loading Embedded fonts #14934
Labels
a/embedded fonts
external-hotrestart
p/iOS 🍎
s/unverified
New report that has yet to be verified
t/bug 🐛
Comments
|
Just added a project that reproduces the crash based upon your WorkingWithFonts sample project so the crash stack trace is shorter but terminates in the same call tree: Show/Hide Example Project crash stack trace |
|
Thanks for the report @bakerhillpins like in #14936 are you using Hot Restart? |
|
@jfversluis Do you mean "Hot Reload" in Tools->Options->Debugging->Hot Reload? "Hot Restart" isn't showing up as an option/command. It was enabled but I've disabled it in the Options and it still occurs. Even restarted VS after the option change to be sure it started with it disabled. (Should I be disabling it some other way?)
Interestingly, I've noticed that the Apply Code Changes button stays enabled regardless of the Hot Reload setting and the way I read the documentation I thought that it should be disabled?
Also noted that the Documentation says that you need to change the linker option to "Don't Link". The example project has the linker setting as "Link Framework SDKs Only" in the repo but changing that doesn't change the outcome either. It still crashes. |
|
Naming is hard... While the naming is very similar, it does something very different: https://docs.microsoft.com/xamarin/xamarin-forms/deploy-test/hot-restart It allows you to debug your iOS application on a iOS device straight from Windows without having to use a Mac. But since you don't know about it I guess you're not using it? :) |
|
Well, what you're describing is exactly what I'm doing, I'm debugging the app directly on an iPhone 12 pro/iPhone 7 device so I must be using that. Referencing the link you provided it states:
Odd though that typing Hot Restart into the search box comes up with no results?
Anyway, disabling this feature forces me to run on an iOS simulator with iOS 15 and it works. |
|
Ah funny how you use this thing without knowing the actual name. Not that I blame you! 😄 OK, great, that at least gives us some direction of when and how this is happening. Not sure if that makes it easier to come up with a fix though. |
|
Yea, "Hot Restart" somehow equating to debugging on a physical device is not a connection I would make. But yes, I feel the pain of trying to come up with naming that's enlightening. |
|
@jfversluis Since this problem exhibits the same relationship to Hot Restart (only occurs on a device - works on an emulator/Hot Restart disabled) I figured I'd add the crash info here so you have it. I could probably build up a 2nd example program but I need to move forward on other things today so it might be end of week. I'm launching an Rg.Plugins.Popup.Pages.PopupPage and I get the following Unhandled Exception: Rg.Plugins.Popup 2.0.0.11 is referenced through Prism.Plugin.Popups Version=8.0.76 |
|
Unfortunately this doesn't help me much, sorry, I appreciate the help and thinking with me though! A reproduction is ofter best. But being honest, the Hot Restart stuff is also something that is a bit outside of our direct circle of influence. I will see if I can get someone to look at it, but wouldn't hold my breath. If you could get those reproductions without spending too much time that would be always helpful though! |
|
Ok, I'll work that up.
Should I be writing these up under some other product? VS perhaps? |
|
Let me first see what I can do with this one and getting some attention on it. I would recommend you to report it through Visual Studio by going to Help > Report a problem. You could still do that to get some extra attention. There is a chance they will still transfer that here though 😅 |
|
Hi guys, (https://developercommunity.visualstudio.com/t/iphone-ios-151-physical-debug/1572333 |
|
Seems you could add some detail to that as well @bakerhillpins! Thanks @angelru |
@jfversluis Yes it does..... @angelru Followed your link to the VS issue and noted the following question from Mauro Agnoletti [MSFT]:
Please report to them that there is no crash when I plug my iPhone into my Mac Mini and debug using the Remote Device. EGAD is it slow to build and deploy though. Probably network related. |
|
As I'm also experiencing the same issue, I took the liberty to also add my observations to the ticket above. |
|
As the linked support ticket (https://developercommunity.visualstudio.com/t/iphone-ios-151-physical-debug/1572333) points out it seems to be something in VS or another underlaying framework and not so much Xamarin.Forms. Please follow up in the linked ticket. Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I'm unsure when this actually started happening but I'm now getting a native crash in iOS 14.8.1 (iPhone 7 and iPhone 12 pro) when I navigate to a Tabbed page with 4 tabs, one of which is loading up FontAwesome Brand fonts (social media icons). I've got a Master/Detail based project. I can navigate to other detail pages that have tabbed pages with no issues. If I remove the page loading fonts it works. This happens every time I navigate to that page.
Steps to Reproduce
I'll work on an example project to reproduce it.
Expected Behavior
No crash
Actual Behavior
Crash
Basic Information
Version with issue: I've tested with 5.0.0.2125 and 5.0.0.2244 and they both crash. It previously worked with 2125 but I've updated both iOS and Visual studio since my last known working sessions.
Platform Target Frameworks:
Android Support Library / AndroidX Version:
NuGet Packages:
Affected Devices: iPhone 7 and iPhone 12 pro are what I have on hand
Environment
Show/Hide Visual Studio info
Reproduction Link
Here's a project that reproduces the crash based upon your WorkingWithFonts sample project so the crash stack trace is shorter but terminates in the same call tree.
WorkingWithFontsIosCrash.zip
Workaround
Not loading the page that consumes the embedded font removes the crash. Not really a solution but it doesn't crash there.
UPDATE - see this comment below
The text was updated successfully, but these errors were encountered: