CODEWITHSUNDEEP
androidgoogle-nearbygoogle-nearby-connections
Christian Jensen
Christian Jensen

Reputation: 41

Nearby Connections API: Cannot access received file on Android 10

I am following this guide with the goal of transferring an image file which on the receiver side should be uploaded via a REST API.

Android 10 blocks access to public folders like the 'Downloads' folder in which all received files from Nearby Connections API are stored in, in a 'Nearby' folder.

File payloadFile = filePayload.asFile().asJavaFile();

I have a Payload object, and as the guide suggests the code above should get the file. Unfortunately the above code returns null when targeting api 29 and running on an Android 10 device. Works fine on earlier Android versions.

I can get the ParcelFileDescriptor by doing File payloadFile = filePayload.asFile().asParcelFileDescriptor(); but not sure how to access the file then?

Via the ParcelFileDescriptor I have tried reading the file in the following ways but I always get some kind of permission or bad access exception:

BitmapFactory.decodeStream(FileInputStream(payloadFileDescriptor.fileDescriptor)) or BitmapFactory.decodeFileDescriptor(payloadFileDescriptor.fileDescriptor)

The file is stored correctly in the Downloads folder as I can see and open it via a file browser app.

Also tried accessing via a content resolver (MediaStore.Downloads.EXTERNAL_CONTENT_URI and MediaStore.Images.EXTERNAL_CONTENT_URI) but no luck.

A note here is that the files are save with no extension, so maybe that's why Mediastore can't find anything?

I use "com.google.android.gms:play-services-nearby:17.0.0".

As mentioned I really want to receive a file and upload it. Is this totally impossible with Nearby Connections API on Android 10?

Upvotes: 4

Views: 313

Answers (1)

Prerak Mann
Prerak Mann

Reputation: 803

Nearby connections 18.0.0 has been released. You can now do this -

if (VERSION.SDK_INT >= VERSION_CODES.Q) {
        // Because of https://developer.android.com/preview/privacy/scoped-storage, we are not
        // allowed to access filepaths from another process directly. Instead, we must open the
        // uri using our ContentResolver.
        Uri uri = filePayload.asFile().asUri();
        try {
          // Copy the file to a new location.
          InputStream in = context.getContentResolver().openInputStream(uri);
          copyStream(in, new FileOutputStream(new File(context.getCacheDir(), filename)));
        } catch (IOException e) {
          // Log the error.
        } finally {
          // Delete the original file.
          context.getContentResolver().delete(uri, null, null);
}

Upvotes: 1

Related Questions