Liam O'Boyle

> upvote (is there a better way to do this?) Yes, use 👍 on the issue

Merged! > Hello, if anyone's interested in how to do this properly on iOS, including custom nonce, with `expo-auth-session`, the code is [here](https://github.com/react-native-google-signin/google-signin-next/blob/feat/supabase-nonce/supabase.md). However, please note it's not publicly available,...

As per my note on https://github.com/expo/expo/issues/33658#issuecomment-2998136489, this seems to be a new architecture issue; we only experience it with the new architecture enabled, even on Expo 53, same code and...

@Ubax yes, it's a problem with `5.1.0`, I'm already using it (only ran into this after upgrading to Expo 53 + enabling new architecture, no problem with the upgrade so...

However `5.1.1` plus use of `dangerouslySingular` has things working for me.

@Ubax , [as I noted here `5.1.1`](https://github.com/expo/expo/issues/37213#issuecomment-3021847176) works for me - https://github.com/expo/expo/pull/37086, I expect, which [was in `5.1.1`](https://github.com/expo/expo/blob/main/packages/expo-router/CHANGELOG.md#511---2025-06-26).

Also running into this with expo 53 (and was not a problem for us _before_ expo 53). Issue should be possibly be reopened. We are not using `getId()` at all,...

I can build locally with no problems using `--local` but I get the OP's error when using cloud build. I'm confused as to what `jest` is doing in there at...

@danstepanov I'm using the current `canary` version. I note your comment about 4.1 being released; should we be upgrading? The guidance in the README put me off. ``` npm ls...

Update: I still have no idea why `jest` is involved at all but allowing more memory as suggested above does get things working for me 🤷