Fix runtime version that update files are copied to in package.json #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simple PR fix:
2throughout the client code. However, when you runyarn expo-publish, it copies the export toupdates/1instead ofupdates/2. As a result, when the manifest endpoint is called, it doesn't detect the new update.updates/$directoryfolder ahead of time to prevent errors like./scripts/publish.sh: line 14: updates/2/1762392374/expoConfig.json: No such file or directoryDebugged live with Cedric ;)