How To Store API Keys For Staging & Production Environments

[@iharandreyev2497]

Why is this approach "safer" than just putting API keys into the source code?
AFAIK plists are not encrypted, so we're facing the same issue here as in `UserDefaults` vs `Keychain`, meaning a hacker can access these plists without a lot of hassle.

[@dima4173]

Would this works outside of Xcode meaning app in the appstore

[@MoAdel92]

Thanks a lot very informative video

[@sabuein]

Thank you very much.

[@kelvinfok]

Pleasure!

[@waheedafolabi6929]

Thanks 🙏 for the guide Kelvin. So much love from me…take care of your child 👦 and I pray 🙏 for the child’s restoration of good health

[@kelvinfok]

Thank you, take care :)

[@vasumudiraj3785]

I found a production api key when testing on staging environment. What's impact?

[@kelvinfok]

Sorry I don’t understand your question

[@vasumudiraj3785]

I am penetration tester. Testing on a staging environment and found one production api key is hard-coded in js file at client side.
How can I use that production key to show some impact ?

[@miguelgonzalez3329]

What would be a better practice instead of using this approach?

[@kelvinfok]

I don’t know of a better approach. Even if you are working with REST service, you typically toggle between 2 sets of APIs

[@amitjoshi6137]

🙏 thanks

[@kelvinfok]

Hope you found it useful!