chirpy
Member
AppDelegate is usually for detecting app lifecycle events, the OS sends different signals when the game is launched/paused/resumed. The extension may work if it does not have to initialize right after the game launches, but depending on what methods are defined in the class, things may go wrong when app is paused/resumed.Thanks @chirpy ! It seems some variation of what you described was not fixed in this 2.3.1 build. I ended up removing the "App Delegate Class Name" that was specified in the Extension and then everything worked, including the functionality of the extension which I thought might stop working because I had cleared that field naming the App Delgate code!
I updated my ticket with YoYo, so hopefully they can have a look at it and sort it out. At this point, I have no idea what that field is for on the extension since being there doesn't seem to be required.
Replacing everything that's trying to check whether the superclass responds [*] to said lifecycle signal should make the chaining work as intended.
[*] We need to replace all
[self superclass] instancesRespondToSelector
in app delegate classes (.mm files) with
[${YYExtAppDelegateBaseClass} class] instancesRespondToSelector
And then, build from GMS2 again to regenerate the .xcodeproj (so GMS replaces the ${} variables)