Team,
Seems like if we have "associatedDomains" on app.json, Expo CLI treats those entitlements as requiring code signing even on simulators, so it runs the code-signing check.
This ends up requiring on Apple Developer account when app is ran as a dev build on a iOS Simulator.
Maybe not an issue, but as someone who does not have a Apple Developer account I had to remove the "associatedDomains" to run the app on a iOS Simulator without code signing.
Maybe this is required for Thirdweb to function correctly, after I removed them I have only tested wallet connection via Google Account, since in the iOS Simlulator the App Store is disabled (by default) and I couldn't download MetaMask.
Team,
Seems like if we have "associatedDomains" on app.json, Expo CLI treats those entitlements as requiring code signing even on simulators, so it runs the code-signing check.
This ends up requiring on Apple Developer account when app is ran as a dev build on a iOS Simulator.
Maybe not an issue, but as someone who does not have a Apple Developer account I had to remove the "associatedDomains" to run the app on a iOS Simulator without code signing.
Maybe this is required for Thirdweb to function correctly, after I removed them I have only tested wallet connection via Google Account, since in the iOS Simlulator the App Store is disabled (by default) and I couldn't download MetaMask.