Exiting the main method "freeze" the Android application

[Misopeth]

I'm trying to use SFML to implement a NativeActivity in a larger project.
First a non-native activity is started, after a while this activity start the SFML NativeActivity and when the user press the "back" button (that trigger a sf::Event::KeyPressed with event.key.code == sf::Keyboard::Escape, as sf::Event::Closed doesn't seem to ever be triggered) the NativeActivity closes and the non-native activity should take back the control, but instead it is "freezed" (non-responding).

I copied Android.mk, Application.mk, main.cpp and the needed part of AndroidManifest.xml from the android example.
I'm using SFML 2.3.2.

Am I missing something in the app or window lifecycle?

[Mario]

Does it work, if you skip the Java activity? I suspect you're triggering some undefined/unexpected behavior.

[Misopeth]

It works, but only because when the NativeActivity stops the entire application is closed, so there's nothing that could go wrong.

[Mario]

Would be nice if you could try to track this down or provide a minimal example doing what's causing your issues. I only have minimal experience with writing Java apps, so not that proficient with that.

[Misopeth]

I'm pretty new to C/C++ programming, so I don't really know how to track down the problem.

[maxwell79]

I also am encountering this on Android 4.4.2.