No code here, just an observation from a month of developing for iOS. There can be a delay on any action taken in the App Store Connect console. Upload a build, add compliance, add testers: sometimes the result of your choices aren’t reflected in the App Store Connect console for minutes, up to hours. Patience. Instead of rebuilding or rage-clicking, just wait a reasonable amount of time for the processes to complete. ...
When working on a React Native app on the iOS side, switching between branches with different dependencies can wreak havoc on your development environment. To ensure they’re you’re running the right libraries, blow everything away and start over: rm -rf node_modules && yarn && (cd ios && pod deintegrate && pod install) Replace yarn with npm install if you’re using NPM.
To get mobile scroll behavior on the XCode Simulator, inside the simulator window you must left click, then scroll.
The ‘shake’ is an important React Native feature; it opens the In-App Developer Menu. This menu lets you reload, open the inspector, monitor performance, and more. To ‘shake’ your simulated device, press ^ ⌘ Z. An alternative hotkey is ⌘ D.
When you push an iOS build to TestFlight, what’s the experience for your testers? Do they need to opt-in to test the latest build? Speaking anecdotally as person who has pushed a build and plans to test it today, when you add that build to your test group, it is automatically downloaded as the default for each of your testers, replacing the previous build. You can visit the TestFlight app on your phone to see the apps you can test. The latest build (build number, an integer, not the SemVer version) should be automatically downloaded to your device.
Don’t miss my next essay
Hear from me immediately when I post: no ads, unsubscribe anytime.