Is it possible to have the same behaviour with startActivityForResult

I have a use case that an **App A** calls my **App B** through `startActivityForResult`.

Current behavior:
after `triggerRebirth` call, app A is called back but the `intent` sent by App B is null a lot of times.

is there any workaround about having `intent `data not null?

Start with the startActivityForResult flow and the triggerRebirth call described in the issue. Trace the callback intent from App B to App A and determine whether preserving non-null intent data is supported; done means documenting a verified workaround or clearly stating the limitation.

Written by the indexing model from the issue text.