Localization update #40
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Observed when using
DMPasscodeon a device with Face ID configured, thekeywas being returned from the customNSLocalizedStringmacro (instead of the localized string). This was causing aNon-empty localizedReason must be providederror to be thrown. The remedy for this is found in the 3rd commit below; the first 2 clean things up.localization-update - Project settings modernization.
DMPasscode&Podsproject.Base Internationalization.:exclusive => truefromPodfile, as it is an unsupported option.platform :ios, ‘8.0’toPodfileto resolve CocoaPods warning.podspecto version2.1.0.pod installfromExampledirectory.localization-update -
Implicit selfwarning resolutions.self ->in a number of places to resolve warnings.localization-update - Resolve
NSLocalizedStringmacro collision.NSLocalizedStringmacro, as it was causing issues when leveraged from Swift code.NSLocalizedStringFromTableInBundledirectly.NSFaceIDUsageDescriptionto example appInfo.plist.