Fixed Swift 5.2 load issue, which doesn't fire anymore the initial load method #80
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.
Fixes #78
From Xcode 10.4 and Swift 5.2, there is an issue that doesn't allow Wormholy to work correctly since the initial method which uses an extension of UIApplication doesn't work anymore.
The new solution implemented is based on this.
This method works like a starter engine for Wormholy. We will call
appWillLaunch()
method in Swift (under theStarterEngine
class), whendidFinishLaunchingWithOptions
is fired.This is the flow:
StarterEngine
receive aUIApplicationDidFinishLaunchingNotification
appWillLaunch()
method underSwiftySelfAwareHelper
Testing
@kealdishx since you worked on the initial implementation #52 of the solution based on the UIApplication extension, I'd like it if you can check if everything continues to work correctly.