Open GabrieleGervasi opened 8 years ago
This also causes some other issues as well, that are still present even with the fix you linked. When it creates the second activity, it creates a new instance of mEditBoxHelper
in Cocos2dxActivity
. The problem with this is when it creates a new instance of that object, it clears out the static list mEditBoxArray
in Cocos2dxEditBoxHelper
. If you have an EditBox on screen and do the same steps you've described above, it no longer has those EditBox's in mEditBoxArray
and cannot open the keyboard or accept input.
Steps to Reproduce:
The problem seems to be related to android issues reported in this answer: http://stackoverflow.com/a/16447508
I managed to solve with answer workaround, but unfortunately i'm totally inexperienced in android activities. Note that with these steps the issue will only be present first time you install and launch the app, if you restart this doesn't happen. There are others methods for this to happen as for example launch the app from play store, return on device home without close, clicking app icon.