Dav
> @ChromeQ I have merged a change that will allow you to change this setting for managed projects... new release will happen soon. Excellent @douglowder I will take a look...
I have investigated and found that expo start script calls `validateDependenciesVersionsAsync` in [startAsync](https://github.com/expo/expo/blob/dfb87e117b521c8531bdf42a42be12fbebe8b707/packages/%40expo/cli/src/start/startAsync.ts#L125) The difference between sdk48 and sdk49 is the `options.devClient`. In v48 the option is set on a...
On a slightly related note, I'musing a development client build (not Expo Go) and I've always seen references in the docs to say you need to run `expo start --dev-client`...
Confirming this issue is still present in v1.2.0
@loopingz Bumping this one to see if this issue can be fixed since the #1182 fix did not resolve it. Thanks
Same problem as @pkreipke once adding OneSignal to the mix, now every build incorrectly says provisioning file is invalid and generates a new one, next build the exact same thing....
@d8vjork I also ran into this error and managed to get around this problem by using [patch-package](https://www.npmjs.com/package/patch-package) to simply update the version of com.google.android.play:app-update to v2.1.0 as per this commit:...