Dev client distribution via test flight
A
Abdullah Hilson
When we try to publish a dev client build to tesflight, the build is rejected saying that it uses Non public APIs. I believe it would be useful to distribute the dev client via tesflight to make the distribution easy inside the team.
The exact error message is:
> ITMS-90338: Non-public API usage - The app references non-public selectors in MYAPP: _isKeyDown, _modifiedInput, _modifierFlags. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
I believe it is caused by this: https://github.com/expo/expo/blob/main/ios/Exponent/Kernel/DevSupport/EXKernelDevKeyCommands.m#L78-L81
Max von Webel
I wrote a Expo module to fix this issue: https://github.com/343max/testflight-dev-deploy . Also I created a PR to allow a workaround in React Native https://github.com/facebook/react-native/pull/46692
George Khromchenko
I think non public API's related to keyboard handling from console, but we don't need it in TestFlight. It would be nice just Expo Go alternative with ability to load any published branch, built with version of SDK that we use in production and our set of config plugins.
George Khromchenko
Since Expo is going to deprecate others than the latest SDK's in ExpoGo, AdHoc only dev client builds will degrade developer experience.
Now our QA team and designers using Expo Go for quick preview of our pull-requests, but recommended workflow for dev-client is to install AdHoc builds to each device, and it would be difficult to have updated version for all our team.
Ability to have special version of dev client in TestFlight will be very useful for previews distribution.