Problen with distriqt share ane

Boc89

Hello everyone!
I've had a problem for several days with file sharing using distriqt's share extension.
I save csv files in applicationStorageDirectory. It works and I can load them in my applis.
I'm trying to set up a share for these files, but it's not working... and I can't figure out where the error is coming from!
Here's my code:

var f = File.applicationStorageDirectory.resolvePath("FileName");
trace("f.nativePath :   " + f.nativePath);
trace("Share Supported :" + Share.isSupported);
trace("Share Version:   " + Share.service.version);
if (f.exists) {
	var options: ShareOptions = new ShareOptions();
	options.title = "Partager avec ...";
	Share.service.addEventListener(ShareEvent.COMPLETE, share_shareHandler);
	Share.service.addEventListener(ShareEvent.CANCELLED, share_shareHandler);
	Share.service.addEventListener(ShareEvent.FAILED, share_shareHandler);
	Share.service.addEventListener(ShareEvent.CLOSED, share_shareHandler);
	Share.service.shareFile(f.nativePath, "FileName", "text/csv");
			function share_shareHandler(event: ShareEvent): void {
				trace(event.type + "::" + event.activityType + "::" + event.error;
			}
		} else {
			trace("File doesn't exist")
		}

f.nativePath is ok
Share supported is true
Share version is 7.6.0
..and share failed : Could not access the file.Check WRITE-EXTERBAL_STORAGE permission and FileProvider.
I think i don't need permission for readind or writinq in ApplicationStorage Directory, and FileProvider is good ...

In the manifest, i have :

<android>
	  <manifestAdditions><![CDATA[  <manifest android:installLocation="auto">
	  <uses-sdk android:minSdkVersion="19" android:targetSdkVersion="30"/>
		 <uses-permission android:name="android.permission.CAMERA" />
		  <uses-feature android:name="android.hardware.camera" />
		 <uses-permission android:name="android.permission.INTERNET"/>
		<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
		<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
		<application>
			<activity android:name="com.distriqt.core.auth.AuthorisationActivity" android:theme="@android:style/Theme.Translucent.NoTitleBar" android:exported="false" />
			 <activity
                        android:name="com.distriqt.extension.scanner.zbar.ZBarScannerActivity"
                        android:screenOrientation="portrait"
                     />
			<provider
			android:name="com.distriqt.extension.share.content.ShareFileProvider"
			android:authorities="com.multimaths.scanscores.sharefileprovider"
			android:grantUriPermissions="true"
			android:exported="false">
			<meta-data
				android:name="android.support.FILE_PROVIDER_PATHS"
				android:resource="@xml/distriqt_share_paths" />
		</provider>
	</application>
	</manifest>]]>
		</manifestAdditions>
 	</android>

FileProvider is declared at distriqt with the right name, and the corresponding extensions... I really don't understand what's wrong!
If anyone can enlighten me, it would be incredible!

FliplineStudios

I just checked my own app that uses that ANE, and it looks like the only difference for me is for the provider android:authorities -- with mine I have the "air." prefix included since that's what it ends up being once AIR packages it.

So within the application xml, near the top I have:

<id>com.flipline.myappname</id>

and within the provider, I have:

android:authorities="air.com.flipline.myappname.sharefileprovider"

Boc89

FliplineStudios
Hello ! Thank’s for reply !
I didn't put the air prefix when I added the application to my distriqt account. It usually works fine, but I'll give it a try tomorrow, thanks for the tip!

Boc89

No, it's not much better, unfortunately...

2jfw

I think i don't need permission for readind or writinq in ApplicationStorage Directory, and FileProvider is good ...

No quite sure about this.
Have a look at the AIR release notes at point 5.4 Android File System Access.

Requesting file system permissions has to be handled in a similar way, with permissions either
granted for a file or for a folder tree. The “File.requestPermission()” function therefore looks at
the native path of the File object this is called on, and decides whether to show a file open intent (if
there’s a normal path or URL in the nativePath property), or to show a folder selection intent (if the
path ends in a forward-slash), or whether to just ignore the call with a ‘granted’ response and then
wait for later permission requests for individual files (if the File object has not had a nativePath set).

from e.g. here:
https://airsdk.harman.com/api/versions/51.1.2.1/release-notes/Release_Notes_AIR_SDK_51.1.2.pdf

You could check if requestPermission() will help..

Boc89

Hi there!
Thanks for the reply! In fact, the problem came from the distriqt share ane which doesn't work with Uri but only with File objects. I couldn't manage with this one, and pol2095 gave me a solution with his own Share ane, which works with URIs without any problem. Combined with his saf ane, everything becomes easier on Android, thanks again to him!