Repository navigation
Explain how the version and build number decide when code updates - #573
Merged
Merged
Conversation
The app only extracts its bundled Laravel code when the version number or build number changes, so a rebuild with the same pair keeps running the old code. Say that plainly, and tell people to bump NATIVEPHP_APP_VERSION_CODE before each build they install. Also fix the claim that native:release bumps the build number. It only bumps the version. native:package bumps the build number, and native:run never does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Docs side of NativePHP/mobile-air#584.
Outside
DEBUG, a mobile app only extracts its bundled Laravel code when the version number or the build number changes. A rebuild installed with the same pair keeps running the old code. The configuration page described the comparison in an aside but never said what it means in practice, so people ended up uninstalling to see their changes.What changed:
getting-started/configuration.mdcalls the two values "version number" and "build number", says the app re-extracts if either one changes, and adds a paragraph after the aside saying to bumpNATIVEPHP_APP_VERSION_CODEbefore each build you install.getting-started/development.mdadds one sentence to the "Rule of thumb" aside, linking back to that section.publishing/introduction.mdandpublishing/ios.mdsaidnative:releaseincrements the build number. It only bumps the version.native:packageincrements the build number, andnative:run --build=releasedoesn't, so the intro now says to bump it yourself before testing a release build on a device that already has one installed.Worth checking: the new link in
development.mduses the anchor#codenativephp-app-versioncode, following the patterninstallation.mdalready uses forNATIVEPHP_APP_ID.🤖 Generated with Claude Code