Hi everyone, I hope you all are safe and healthy. Hi iOS developers, have you ever fear while accessing an array? If you have, then you are in the right playground to control your fear.

😵‍💫 Problem

Have you ever get an error Fatal Error: Index out of range while trying to get value at a specific index? This error is trivial but dangerous because it will lead crash to your app.

💡 Idea

We could avoid that error with thesubscript keyword in Swift, yeay 🥳. Let’s get in touch with the subscript keyword. What is the subscript keyword? and how does it works?

What is subscript keyword?

subscript is a shortcut for accessing the member elements of a collection, list, or sequence. But in another context, you can use subscript like computed getter and setter of your struct or class. You can click here to know more about subscript .

How does it work?

subscript is like computed getter and setter . You can write your incredible code for getter and setter . Here is the default syntax of using the subscript keyword.

🎯 Action

Let’s back to the problem. We could take advantage after we know a glimpse of subscript keywords in Swift. So, here is the code for accessing your array safely.

✨ Summary

You can take advantage of using the subscript keyword to access your object or collection.

Pros

• You can save your time complexity by using this way instead of using both contains() and contains(where:) .
• Safely access the value at a specific index.

Cons

• This approach is suitable if you just know the index and don’t know the value inside your collection.
• It will be good to have a checker in our compiler because you can’t give nil as the new value.

👋🏻 Closing

Thank you! I hope this helps you. Please let me know if you have any trouble or any discussion about this. Never stop learning! 🔥

Playing with Subscript keyword to access Array safely was originally published in Geek Culture on Medium, where people are continuing the conversation by highlighting and responding to this story.

🙂 Introduction

Hi everyone, I hope you all are safe and healthy. Hi iOS developers, do you work in a team? Have you had a conflict with the pbxproj file? If yes, this time I want to invite you to play with XcodeGen to avoid pbxproj file conflicts.

😵‍💫 Problem

Have you had a conflict with the pbxproj file? For example, you and your teammates both add files in the same directory location. When you want to merge your working branch into a development branch or feature branch, then the conflict happens 💥🤯.

💡 Idea

We could avoid the pbxproj file conflict by using supporting tools. Here I recommend you guys to use XcodeGen.

Why?

• It’s easy to use to operate. It means when your project configuration is ready, you only need to open your terminal and run xcodegen.
• It supports to create Info.plist
• It supports customizing your project Build Setting and Build Phase . Yes, it also supports entitlement configurations.
• Allow you to run any commands before generating the xcodeproj file.
• Allow you to run any commands after generating the xcodeproj file.
• No longer need to push xcodeproj and xcworkspace , Info.plist is optional.

Why not?

• It’s a bit of a hassle to customize the project Build Settings and Build Phase . Because you need to know the key of configuration that the value you want to set. My way is you need to open the pbxproj file with another editor application to see the complete key.

🎯 Action

I will share my personal project configuration that already implements XcodeGen. The project configuration will be written in a project.yml file. You can make mine as your reference in making your project configuration.

🎉 Summary

There are several ways to avoid pbxproj file conflict. But for me, this is the best way and might be your answer to avoiding conflict and your worry when you want to merge.

Probably the hard part is when you want to set Build Setting or Build Phase , there will be a question in your head, “is it possible or not ?”. Take action to try will helps you. Good luck 👍🏻

👋🏻 Closing

Thank you! I hope this helps you. Please let me know if you have any trouble or any discussion about this. Never stop learning! 🔥

Playing with XcodeGen to avoid pbxproj file conflicts ⚠️ was originally published in Geek Culture on Medium, where people are continuing the conversation by highlighting and responding to this story.

🙂 Introduction

Hi everyone, I hope you all are safe and healthy. This time I want to invite you to playing with Build Configuration in XCode to separate environment.

🎯 Challenge

So, maybe in your current project you are starting to need to separate which environment is for development, QA, staging or maybe production. If yes, you are playing on the correct ground.

🏃🏻 Steps

First, open your project with XCode and then go to project navigator, select your project, and choose Info.

Second, focus with the Configuration section and then let’s duplicate Debug and Release as many environments as you need in your project.

Debug is a configuration that XCode use when you run in simulator or iPhone.

Release is a configuration that XCode use when you want to export your app as an ipa file or publish to App Store Connect

So, for now, let’s create three environments, development, staging, and production.

Third, let’s create scheme for each environment configuration that we have created.

Fourth, we will edit each scheme that we have created in previous step.

Run section is about your XCode will build and run the target on the selected device or simulator.

Test section is about your XCode will build your target and run Unit and UI tests.

Profile section is about your XCode will build and run your target on the selected device or simulator with an Instruments tool of your choosing (Leaks, Allocations, etc.). That’s why we need Debug for this Build Configuration.

Analyze section is about your XCode will build your target using the static analyzer and let you know of certain types of bugs in your code. That’s why we need Debug for this Build Configuration.

Archive section is about your XCode will build and make it your project as archive file or ipa file. That’s why we need Release for this Build Configuration.

That’s why we need Debug for Build Configuration in Run, Test, and Analyze sections. Also that’s why we need Release for Build Configuration in Profile and Archive sections.

References: https://stackoverflow.com/a/32767816

Fifth, this is the last step, yeay! We will add custom flag for Swift Compiler. So we can manage which code that we want to be executed for specific environment.

⭐️ Conclusion

When your project gets bigger and requires separation for each environment (development, staging, production) this method will be one of the solutions you can use.

👋🏻 Closing

Thank you! I hope this helps you. Please let me know if you have any trouble or any discussion about this. Never stop learning! 🔥

Playing With Build Configuration in XCode to Separate Environment was originally published in The Startup on Medium, where people are continuing the conversation by highlighting and responding to this story.

🙂 Introduction

Hi everyone, I hope you all are safe and healthy. This time I want to share about my experiment of playing with workspace. Yes, it’s xcworkspace.

🎯 Challenge

So, here are some challenges for my experiment. I have one application that will be published in various countries with some different features. But also means there will be some same features.

🏃🏻 Steps

First, define the structure directory. Here we try to design our structure directory will look this at the end.

Second, open XCode and create a new workspace. For me, I will name it with App.xcworkspace.

Third, you have empty xcworkspace and now we will add a new project. Yes, a new xcodeproject. You can press Shift+Command+N for access keyboard shortcut to create project.

Set your Add to: and Group: field with your workspace

After you hit create button. Your project directory and XCode will look the following screenshot. Exellent! You have one project inside your workspace now.

Fourth, continue it for the other projects. In my case, I will add App-SG.xcodeproject and App-US.xcodeproject.

⭐️ Conclusion

Now we have 3 different projects in one xcworkspace. Next I will share how to add shared framework that we can use in each project.

👋🏻 Closing

Thank you! I hope this helps you. Please let me know if you have any trouble or any discussion about this. Never stop learning! 🔥