Hello,
After reading the Config File Elements documentation and a-lot of trial and error I was able to get this to mostly work, i.e. tapping a link to the "android:host" shows the Android chooser with my app as an option along with Chrome.
The trick was to create an activity-alias containing the intent-filter instead of trying to craft an xpath for "parent" that injected it into the default activity.
This is a hack and has issues and I would much prefer a method that allowed me to add a second intent-filter to the default activity.
Is this possible? I am by no means an Android or xpath expert but the merging of the XML never resulted in the output I was after. I don't know what xpath to supply for parent that says: 'In the first activity and AFTER the existing intent-filter closing tag add another intent-filter'.
For example if the following were legal XML it would do what I want:
because once PGB merged it the result would then be:
Which is what I am after.
Can this be achieved with the current PGB (3.6.3)?
After reading the Config File Elements documentation and a-lot of trial and error I was able to get this to mostly work, i.e. tapping a link to the "android:host" shows the Android chooser with my app as an option along with Chrome.
The trick was to create an activity-alias containing the intent-filter instead of trying to craft an xpath for "parent" that injected it into the default activity.
This is a hack and has issues and I would much prefer a method that allowed me to add a second intent-filter to the default activity.
Is this possible? I am by no means an Android or xpath expert but the merging of the XML never resulted in the output I was after. I don't know what xpath to supply for parent that says: 'In the first activity and AFTER the existing intent-filter closing tag add another intent-filter'.
For example if the following were legal XML it would do what I want:
</intent-filter>
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:host="my.appdomain.com" android:scheme="http" />
because once PGB merged it the result would then be:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:host="my.appdomain.com" android:scheme="http" />
</intent-filter>
Which is what I am after.
Can this be achieved with the current PGB (3.6.3)?


cce32