Manifest Merge Tool

#1

I think we didn’t pay enough attention to the new great feature Manifest Merge Tool.

Using this feature we don’t need to ask our users to do this extra step: “please add those lines into AndroidManifest.xml, plist, index.html” and so on.
The whole process of adding library now more consistent and easier for the end user.


The first example is Defold Sharing NE 1.6.0.

Old deprecated manual steps:

Additional steps for iOS

In the case when a user wants to save a video or an image to the gallery iOS will need to show an explanation to the user. Your explanation should be added into your Info.plist:

	<key>NSPhotoLibraryAddUsageDescription</key>
	<string>Your application needs permission to save the content to the gallery.</string>
	<key>NSPhotoLibraryUsageDescription</key>
	<string>Your application needs permission to save the content to the gallery.</string>

Additional steps for Android

Sharing files (images) on Android is quite a bit tricker than on iOS due to the Android permission system. The correct way to share files is via a FileProvider. In order to use the extension on Android you need to add the following to your AndroidManifest.xml file:

<manifest>
	    ...
	    <application>
	        ...
	        <provider
	            android:name="android.support.v4.content.FileProvider"
	            android:authorities="{{android.package}}.fileprovider"
	            android:grantUriPermissions="true"
	            android:exported="false">
	            <meta-data
	                android:name="android.support.FILE_PROVIDER_PATHS"
	                android:resource="@xml/filepaths" />
	        </provider>
	        ...
	    </application>
	</manifest>

Instead of these manual steps, we have new files for the merging tool according to the documentation:
image

We’ve started to change our libraries one by one using this new tool and I want to ask you to do the same with your libraries.
That will make work with Defold and your extensions easier and more pleasant.

Thank you!

15 Likes