Fix fileprovider name #113
Merged
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.
Exposed the bundle_indentifier in cookiecutter and updated the AndroidManifest, replacing
{{ cookiecutter.bundle }}.{{ cookiecutter.app_name }}with{{ cookiecutter.bundle_identifier }}. This removes the underscore/hyphen mismatch and prevents the FileProvider “couldn’t find meta-data” crash for apps whose IDs contain underscores.The Android manifest template currently builds the FileProvider authority from bundle + app_name, e.g. com.example.image_classification.fileprovider (with an underscore). At runtime, Toga’s Android camera code looks for the FileProvider using the hyphenated authority (com.example.image-classification.fileprovider), but the manifest has registered a different authority with an underscore.
By switching the manifest to use {{ cookiecutter.bundle_identifier }}. The authority in AndroidManifest.xml becomes com.example.image-classification.fileprovider, which matches exactly what Toga expects at runtime.
Fixes beeware/toga#3237
PR Checklist: