Amazefilemanager: After saving an image the app throws me to the launcher, not the last used app

[EmmanuelMess]

After saving an image through the share dialog the app throws me to the launcher, not the last app.

[VishalNehra]

That's the framework's problem.

[EmmanuelMess]

It is difficult to find another app that does more or less the same thing, but Google's Photos has an upload feature that goes back to the original app, so it is not a problem in the framework.

[EmmanuelMess]

Prove it is the framework.

[VishalNehra]

Because it's behaviour is different for different device vendors.

[EmmanuelMess]

It is Android, that argument doesn't really make sense.

[VishalNehra]

Hence we can't possibly program for every device vendor out there.
There's nothing we can do if a vendor decides to override finish callback to redirect to their launcher instead of the last app opened.

[EmmanuelMess]

"Their" launcher, I'm using FlickLauncher? I don't think anyone is overriding the finish().

[PiwwowPants]

I can't seem to reproduce this in 8.1 on either Pixel Launcher or FlickLauncher on the master branch.
Is there a specific app being used? Launching in to save through Edge or Chrome returns me back to those apps when I save in Amaze.

[EmmanuelMess]

Will test with Chrome tomorrow.

[EmmanuelMess]

Tested, the issue seems to be of Firefox. With Chrome this issue doesn't exist.