Sorry got this wrong again, the right scheme for the builder app is 
"cn1bldapp". 
See this for more details: 
https://www.codenameone.com/blog/tip-activate-via-url-send-arguments.html
On Wednesday, August 5, 2020 at 2:38:39 PM UTC+3 [email protected] 
wrote:

> Thanks,
>
> Ran with "" and got error:
> D AstcTechMobileApp: [invokeAndBlock2] 0:2:20,93 - Exception: 
> android.content.ActivityNotFoundException - No Activity found to handle 
> Intent { act=android.intent.action.VIEW dat=CodenameOneBuildApp: 
> pkg=com.codename1.build.app }
> 08-05 07:27:01.660 21429 21610 W System.err: 
> android.content.ActivityNotFoundException: No Activity found to handle 
> Intent { act=android.intent.action.VIEW dat=CodenameOneBuildApp: 
> pkg=com.codename1.build.app }
>
> Please see attached log. "*Codename1_1Log.txt*"
>
> Please see screen shot of execute argument in attached pic 
> "AndroidGalaxy5S2ExecuteIntentErrors_2.jpg"
>
> Thoughts?
>
> Regards
>
> On Monday, August 3, 2020 at 10:50:31 PM UTC-4, Shai Almog wrote:
>>
>> You also need to change "customapp" to CodenameOneBuildApp. Sorry missed 
>> that.
>>
>> On Monday, August 3, 2020 at 2:35:39 PM UTC+3 [email protected] 
>> wrote:
>>
>>> Seems like the syntax of this call is suspicious.
>>>
>>> Display.getInstance().execute("intent:#Intent;scheme=customapp;package=com.codename1.build.app;end");
>>>
>>> Getting 
>>>
>>> Thoughts?
>>>
>>> regards
>>>
>>> "08-03 07:27:13.129 25211 25240 D AstcTechMobileApp: [invokeAndBlock1] 
>>> 0:0:12,923 - Exception: android.content.ActivityNotFoundException - No 
>>> Activity found to handle Intent { act=android.intent.action.VIEW 
>>> dat=customapp: pkg=com.codename1.build.app }
>>> 08-03 07:27:13.129 25211 25240 W System.err: 
>>> android.content.ActivityNotFoundException: No Activity found to handle 
>>> Intent { act=android.intent.action.VIEW dat=customapp: 
>>> pkg=com.codename1.build.app }
>>>
>>>
>>> On Sunday, August 2, 2020 at 11:29:44 PM UTC-4, Shai Almog wrote:
>>>
>>>> It should launch for "com.codename1.build.app" although I haven't tried 
>>>> that.
>>>>
>>>> On Sunday, August 2, 2020 at 2:08:54 PM UTC+3 [email protected] 
>>>> wrote:
>>>>
>>>>> I don't know.
>>>>>
>>>>> can you provide the codenameone build app string 
>>>>> ?Display.getInstance().execute("intent:#Intent;scheme=customapp;package=[*path
>>>>>  
>>>>> to codenameone build app*];end"); (Android Only)
>>>>>
>>>>> On Saturday, August 1, 2020 at 11:05:28 PM UTC-4, Shai Almog wrote:
>>>>>>
>>>>>> It looks that it works but the file manager in question doesn't seem 
>>>>>> to support that for some reason. Can you open other apps with this 
>>>>>> intent?
>>>>>>
>>>>>> On Saturday, August 1, 2020 at 4:40:57 PM UTC+3 
>>>>>> [email protected] wrote:
>>>>>>
>>>>>>> Yes,
>>>>>>>
>>>>>>> See attached 
>>>>>>> "AndroidGalaxy5S2com.diamond.apps.filemanager_1ErrorLog.txt"
>>>>>>>
>>>>>>> Additionally, can you provide the codenameone build app string ?
>>>>>>>
>>>>>>> Display.getInstance().execute("intent:#Intent;scheme=customapp;package=[*path
>>>>>>>  
>>>>>>> to codenameone build app*];end"); (Android Only)
>>>>>>>
>>>>>>> On Friday, July 31, 2020 at 10:53:29 PM UTC-4, Shai Almog wrote:
>>>>>>>>
>>>>>>>> I don't see anything in the logs here can you place them as text 
>>>>>>>> somewhere?
>>>>>>>>
>>>>>>>> On Friday, July 31, 2020 at 10:43:09 PM UTC+3 
>>>>>>>> [email protected] wrote:
>>>>>>>>
>>>>>>>>> Thanks Guys.
>>>>>>>>>
>>>>>>>>> I think to put this issue to bed, I would like to get this working:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Display.getInstance().execute("intent:#Intent;scheme=customapp;package=com.diamond.apps.filemanager;end");
>>>>>>>>> However it generates the error attached 
>>>>>>>>> "AndroidGalaxy5S2ExecuteIntentErrors_1.jpg"
>>>>>>>>>
>>>>>>>>> See pic "AndroidGalaxy5S2com.diamond.apps.filemanager_2.jpg" for 
>>>>>>>>> class path from Filemanager app.
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> On Friday, July 31, 2020 at 1:00:08 PM UTC-4, Dave Dyer wrote:
>>>>>>>>>>
>>>>>>>>>> If you've got a dozen little apps that act as modules and 
>>>>>>>>>> cooperate with each other, I would think
>>>>>>>>>> long and hard about just bundling them into a single app.  There 
>>>>>>>>>> are sooooo many ways a gaggle
>>>>>>>>>> of apps can become out of sync and fail to work together, and 
>>>>>>>>>> coordinating changes among them
>>>>>>>>>> is a pain.  Not to mention that you have to keep building and 
>>>>>>>>>> distributing them all.
>>>>>>>>>>
>>>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/563e5575-3885-4847-9840-d30f086892c9n%40googlegroups.com.

Reply via email to