You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our project currently only supports one language, but upon integrating your pod, now it claims to support a myriad: Italian, Japanese, Korean, Portuguese, Spanish, and Traditional Chinese. I'm glad it has this capability, but I think you would agree that your pod shouldn't dictate what languages our app supports. :)
The solution appears to be thus, from a similar example with a Git project Appirater:
Afaik, this is only because Appirater adds all those localization bundles in the root of your app’s bundle. It should not do that. It should have a namespaced resource bundle that contains them and adjust the code accordingly.
As it is now, you can’t even have your own localizations without merging them with those of Appirater, which is bad.
Our project currently only supports one language, but upon integrating your pod, now it claims to support a myriad: Italian, Japanese, Korean, Portuguese, Spanish, and Traditional Chinese. I'm glad it has this capability, but I think you would agree that your pod shouldn't dictate what languages our app supports. :)
The solution appears to be thus, from a similar example with a Git project Appirater:
CocoaPods/CocoaPods#1301 (comment)
Any help with this would be greatly appreciated!
The text was updated successfully, but these errors were encountered: