-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BIT-58: Configure the project to allow customizing bundle identifiers and versions #14
Conversation
No New Or Fixed Issues Found |
512bfd2
to
06363ca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this config setup and the flexibility it gives ! 🚀
@matt-livefront btw, if you want to customize the icon for Dev, we have the icons here |
Thanks, I'll add it! |
a9dbf0b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!! 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love that dev icon!
🎟️ Tracking
BIT-58
🚧 Type of change
📔 Objective
This PR modifies the project configuration to make it easier to swap out bundle identifiers and version numbers. I removed the existing xcconfig files and created a Configs directory for xcconfig files for all targets.
Common.xcconfig
contains common Bitwarden build settings.Local.xcconfig
contains developer specific build settings, which override anything inCommon.xcconfig
.The
Local.xcconfig
file is in gitignore, so developers can put any build settings (like the base bundle ID) in this file and it will override the default Bitwarden settings. This should make it easier to swap bundle IDs for development and QA builds. For example, if you drop the following into that file, you should be able to build for device using a different team & bundle ID.I also had to make some changes to pass TestFlight validation:
NDEF
fromcom.apple.developer.nfc.readersession.formats
.The
NDEF
change was causing the following TestFlight error:From what I could find, it seems like this worked in the Xamarin app because it linked against an older iOS SDK. But on newer SDKs this results in the above error. And removing that format supposedly doesn't affect NFC reading. I added a task to our backlog to confirm that when we get to that point.
📋 Code changes
project.yml
for the version numbers.⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes