The Development Workflow #427
-
So just like you have the whole My fastlane setup is on the simpler side because the use case doesn't involve the same amount of complexity and while most of my questions were answered during a quick browse on the code, I'd like someone to help me out as to what else was being handled in case I miss something.
Then there's the other source code related stuff which I didn't go through in detail but assuming that there's no other environment based values in there and you just use the different variants and targets to separate concerns. Overall, is the above enough to setup the variants or is there anything else that needs to handled before I go with this approach? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @barelyhuman! Hope you're doing well 🙂 I think you've covered pretty much all of what needs to be done. Specifically for Android, you can notice that you need to add the On iOS, you should create separate targets and schemes on XCode and add the targets to your The rest is handled on the Fastlane files, like you mentioned. There are also separate scripts on Hope this helps a bit, and if you have any questions don't hesitate to reach out |
Beta Was this translation helpful? Give feedback.
Hi @barelyhuman! Hope you're doing well 🙂 I think you've covered pretty much all of what needs to be done.
Specifically for Android, you can notice that you need to add the
productFlavours
to yourapp/build.gradle
file https://github.com/standardnotes/mobile/blob/develop/android/app/build.gradle#L182, and add each flavour's icons to the corresponding res folder.On iOS, you should create separate targets and schemes on XCode and add the targets to your
Podfile
, like so https://github.com/standardnotes/mobile/blob/develop/ios/Podfile#L16. You can also create separate icon sets and set them to each target on Build Settings > Asset Catalog Compiler - Options > Asset Catalog App Icon Set Name.…