-
Notifications
You must be signed in to change notification settings - Fork 70
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
Inter_600SemiBold from @expo-google-fonts/inter crashing my react-native app on ios #109
Comments
Having the same issue |
This was a life saver. I also have this problem. Came when updating to expo 51 |
Able to reproduce here. I should note that I believe this is some kind of fault with RN, iOS or the font file itself as:
|
@Gnative GNative Thanks for that post. I had the font issue, which I resolved by removing that 1 font, but I'm still getting the EXEC_BAD_ACCESS errors and have no idea why. I now understand it is part of the font issue. Thank you. |
I might experience a similar problem (same stack trace). However, I don't use Inter_600SemiBold or any Google Fonts at all – instead, I use custom TTF fonts via expo-fonts const [fontsLoaded] = useFonts({
'Cute-Dino': require('./assets/fonts/Cute-Dino.ttf'),
'RedditMono-Regular': require('./assets/fonts/RedditMono-Regular.ttf'),
}); I can't sustainably reproduce the crash, unfortunately. It sometimes occurs when navigating to some screen that includes one of the fonts. I'm still unsure which one is the exact culprit – somehow the stack trace includes "[H]elvetica Oblique", even though I don't make use of that font at all: Stack Trace
|
@alanjhughes I'm still receiving a crash along with a similar stack trace above. I know you merged this fix and have shared my input on this thread, but I am still seeing this with the fix on Expo 51. Downgrading to Expo 50 seems to resolve the issue. This issue is keeping me from upgrading. Do you have any ideas? |
@iM-GeeKy I'll need a minimal example that demonstrates the crash so I can debug it. I've tested against the font mentioned in this issue and I'm not seeing any problems. |
Did you ever resolve this? I'm having the exact same issue! |
I have the same issue, but unfortunately can't reliably reproduce the problem. It is intermittent. |
Shortly after posting my comment above, I noticed that in the issue in the expo main repo it was discussed that expo-font 12.0.7 fixes this issue. For my specific problem, this seems to be the case: I've upgraded to expo-font@12.0.7 and expo@51.0.12 and the crash hasn't occurred again since then. I was on expo-font@12.0.5 before. |
I'm currently on
did a new build and have confirmed it has the fix code along, but am still seeing the issue. |
I actually removed all custom fonts in our project including the Prior to removing those deps I also updated to I'm now convinced its something to do with moving to Expo 51. Our first crash in Prod directly correlates to the day we updated to Expo 51 |
@gm90 to clarify, you're saying you have removed |
@gm90 none of your changes will effect expo go. If you want to remove some of the included dependencies ie expo-font you'll need to use a dev build. Same thing when loading the fonts through the plugin. That won't work in expo go. |
I'm seeing similar behavior, but I'm using development builds. Expo 50 seems to work, but upgrading to 51 seems to bring about the issues. I'd be happy to hop on discord or something and show you the crash if that makes it easier (I haven't managed to reproduce it locally yet, but I can consistently get it to crash in my main project). |
I'm not quite sure what you mean by none of the changes would affect Expo Go? As I was making these changes I was definitely noticing the changes of fonts from one to another etc in Expo Go, and ultimately the removal of the font, effectively causing the app to use what I thought to be the OS default. Are you saying by removing them from In the end I was also doing development builds in an effort to try and Symbolicate the crash reports but I can't honestly say I then ran one of those (it had been a long few days). |
@gm90 Yes, you cannot remove the native code from expo go. Also config plugins will not have an effect on it. You can remove the JavaScript but that's all. |
@alanjhughes I also removed
and sentry seems to capture the error
|
@gm90 I was sort of able to reproduce the example in another project and was wondering if you could try the same. I know this sound super crazy, but if I first caused the crash in my main project (in this case the codebase you cannot share). Then kill everything and start your reproducible example app and see if you get the same error. I realize that sounds bizarre and I've never seen anything like it, but that's the best I've managed to come up with 🤷🏼♂️. I'm not sure this is much help for @alanjhughes . This only seems to be present on Expo 51. Reverting to Expo 50 fixes the issue. Screen.Recording.2024-06-22.at.1.07.58.PM.mov |
Has a solution been identified? |
Wasn't able to reproduce what your seeing here, but still getting the error on our existing repo. Hopefully what @Njaah-0 has found may point us in the right direction as I'm struggling to find anything concrete. We've got a spike with Sentry lined up so may try and bring that forward and see if it sheds any more light |
@alanjhughes @brentvatne, we’re seeing the same behavior after upgrading our app to Expo 51. We’ve reverted back to Expo 50 for the time being. Do you have any insights into this? |
I've not been able to stop it. A couple of times I thought I'd hit on something as I didn't witness it as regularly as I have had and then all of a sudden it'll pop back up. |
@alanjhughes and @iM-GeeKy, we're seeing the same problem @gm90 is describing after moving to Expo 51. The stack trace indicates a weightOfFont(UIFont*) + 400 error, but it seems to crashing when switching screens/tabs. For the time being, we have rolled back to Expo 50. |
Facing the same issue. |
@alanjhughes As mentioned earlier, I'm happy to screen share the issue with you since I can't share my code base. I know it's not the conventional way, but it seems a number of people are experiencing the issue, but recreating a reproducible example is appearing to be difficult. Just let me know, I'm here to help however I can. |
Our team is facing this issue as well. |
@gm90 Are you still facing this issue or have you found a solution? I've updated to the latest version of Expo
and am still seeing plagued by a crash... |
@alanjhughes This is the reproducible example that I used to cause the crash above which behaves like the crash in my private repository. If you have any questions, I'm happy to answer them. |
@iM-GeeKy what is this example demonstrating? This seems to be something to do with an issue with image manipulator that has already been fixed. Updating it fixes the problem |
Sorry, the repo name is misleading as I was reusing an old repo that I used to open an issue in the past. The branch I posted in the link above demonstrates the font related crash folks are seeing. |
We are, but I'm transitioning between projects at work at the moment so haven't been able to dedicate further time to it. That transition should be complete as of Monday so hoping to be able to focus efforts on our app and help out a bit more here. Hopefully @iM-GeeKy has got a reproducible example there 👆. That will help massively I'd imagine. |
Nice one @iM-GeeKy. I was able to reproduce the same crash on your repo: ![]() Looks like @alanjhughes is on the case 👏 Thank you! |
@alanjhughes @gm90 I confirmed expo/expo#30400 resolved the issue! |
@iM-GeeKy nice! Glad to hear it! |
Don't want to be that guy, but bumped to the two increased versions as soon as I saw this go out: 51.0.21 for expo + 12.0.9 for expo-font and definitely felt much more stable. However I've just had a crash for what looks like the same reason 😭 : Are they the same changes you made @iM-GeeKy |
@gm90 Yeah, I updated the dependency and rebuilt for the changes to take affect. I haven't seen it crash yet, but will let you know if it creeps back. |
Hello. @gm90 @alanjhughes I'm getting the custom font crash issue in react-native bare + expo.
![]() |
You'll need to move to 51.0.21 I believe. I still get it in Expo Go on the odd occasion (gone from getting it every 5 minutes to once a week) but our dev builds and prod builds we've not seen it since @alanjhughes pushed his fix ❤️ . |
@gm90 I'm using the expo version 51.0.22. I'm getting the crash "name": "expo", ![]() |
Any luck or a patch? @alanjhughes FYI, the build works fine in the foreground mode. Sometimes, we can repeat the issue in the background mode, or quit the app and open it again. I use the react-native bare, but some libs require the expo, so install the expo in the react-native bare. I don't use the expo font to load the custom font. I only load the fonts with react-native bare. |
hey folks, if you create a new issue with a minimal reproducible example using the latest version of expo-font (12.0.9), we would be happy to look! we have been unable to reproduce any issues on the latest version. i would also verify in your project with |
@brentvatne Ok, let me create a minimal reproducible example. yarn why expo-font |
@lichmac any luck with this? |
@gpawlik1 any solution regarding the font issue? |
No update so far. I might try to replace all the |
@gpawlik1 yes indeed. I get below crashlytics events if they are any help to come up with any idea. So far 4 different crashes from iOS 15 all the way up to iOS 18. Update: Is @expo/vector-icons causing the issue here? Can you explain more? |
I tried many different approaches on loading my custom fonts (or not loading them at all) and the crash remained. |
@gpawlik1 I think the solution is to replace What do you think? |
got the same crash logs in crashlytics as @CostasCF. Is there any fix for this? |
@mrakesh0608 After replacing @expo/vector-icons with react-native-vector-icons crashes are still occurring but are limited to small numbers. |
My app crashes on ios whenever I navigate to a route that makes use of Inter_600SemiBold.
The text was updated successfully, but these errors were encountered: