Android 10: Unable to access later an image that can chosen through Photos/Gallery - file-permissions

Question

This is a variation of the question I had asked the other day and resolved with help.
Android 10: Able to upload a Uri directly but fails with "Permission denial" exception when re-attempted later
Using a combination of ACTION_OPEN_DOCUMENT and getContentResolver().takePersistableUriPermission, I am able to upload later a file that was chosen by user.
But, if the user selects an image through Photos/Gallery to share through our app and if there is no network at that moment, as expected the app needs to attempt the upload later. During this re-attempt, I am facing a "Permission Denial" exception. Please let me know what might be wrong. Appreciate your help.
How the URI is retrieved
callingIntent = new SharedIntent();
callingIntent.action = getIntent().getAction();
callingIntent.type = getIntent().getType();
if (Intent.ACTION_SEND.equals(callingIntent.action) ||
Intent.ACTION_SEND_MULTIPLE.equals(callingIntent.action))
{
callingIntent.uri = (Uri) getIntent().getParcelableExtra(Intent.EXTRA_STREAM);
if (null == callingIntent.uri)
callingIntent.uri = getIntent().getData();
callingIntent.aUri = getIntent().getParcelableArrayListExtra(Intent.EXTRA_STREAM);
}
In the Intent that receives the URI through Photos, we have this -
getContentResolver().takePersistableUriPermission(callingIntent.uri, Intent.FLAG_GRANT_READ_URI_PERMISSION);
To call the the IntentService to which the URI is passed for upload -
intentService.setData(callingIntent.uri);
intentService.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
context.startService(intentService);
But when the startService is called, there is a "Permission denial" exception - "Permission denial: no permissions found for UID...."

Answer 1

You cannot reliably get persistable Uri permissions on arbitrary Uri values. That only works if you get the Uri from the Storage Access Framework, such as your ACTION_OPEN_DOCUMENT scenario. A Uri that you receive from ACTION_SEND or ACTION_SEND_MULTIPLE is unlikely to have been obtained from the Storage Access Framework.
As a result, you have to use that Uri immediately. If you cannot do so, your options are:
Tell the user that you cannot perform their desired operation now, or
Make a local copy of the data now to a file (e.g., in getCacheDir()) while you can, then use and delete the copy later