That will open in an iframe, as there is no ajax=true parameter, maybe that’s the difference, if you have an index in the applications table with ajax=true.
Ralf
Willkommen im EGroupware-Community-Forum.
Bitte beachte: Bedienungsanleitung Forum, EGw-FAQ und richtig posten.
Folge uns: 
Welcome to the EGroupware community forum.
Please note: User manual Forum, EGw-FAQ and post correctly.
Follow us:
$setup_info['myapp']['name'] = 'myapp';
$setup_info['myapp']['title'] = 'myapp';
$setup_info['myapp']['version'] = '0';
$setup_info['myapp']['app_order'] = 8;
$setup_info['myapp']['enable'] = 1;
$setup_info['myapp']['index'] = 'myapp.uimyapp.index';
/* some info's for about.php and apps.phpgroupware.org */
$setup_info['myapp']['author'] = '';
$setup_info['myapp']['license'] = 'GPL';
$setup_info['myapp']['description'] = 'myapp Module.';
$setup_info['myapp']['maintainer'] = array('name' => '', 'email' => '');
/* The hooks this app includes, needed for hooks registration */
$setup_info['myapp']['hooks'] = array(
);
This is the setup.inc file. Should I add ajax=true in the index parameter here and also in the index.php file ?
That depends on you using eTemplate2 and your app does not mess up the other apps running.
Does the problem only happen with a mobile device, or also with a regular browser (which my show better logging)?
Ralf
No we are not using Etemplate. This problem is only on mobile device, on the browser the applications loads by default properly without any error every time we login.
Try again with Chrome switching to a mobile profile. Maybe you get lucky and get a better error-message …
Ralf
Is that a container installation, or how did you make it?
I’m asking because I fear the status app is missing, which is kinda impossible for a container installation.
Ralf
Nope that function is in fw_desktop.js:
But the fw_mobile.js does not have that method:
That’s probably the problem. Not sure why it only stalls your app, and not any of ours …
@hadi.nategh Should that method (execPushBroadcastAppStatus) be moved from fw_desktop to fw_base, so it’s also available in fw_mobile?
@vishakha: you can try to define it in your pixelegg/js/fw_mobile.js sources to see if you app then starts working.
Ralf
Hadi moved the method to the base-class:
This will be part of the maintenace planned for today or tomorrow.
Ralf
I also tried to install your “Example” custom app from git and the same thing happens with that too
Maybe that will give you the reproducing scenario
By default mail application runs, only when you select your custom app and then logout, start a new session with the custom app, it stalls
Not sure what you’re talking about: I wrote you that we found and fixed the problem.
Did you apply the patch and does it work for you?
Ralf
Sorry, I applied the patch and it didn’t work. So just to give you a reproducing scenario, I tried the “Example” app on mobile
Can you check in the example app which was created as a demo by you guys for custom application. I saw the same issue with that application.
Hi Vishakha,
I am not able to reproduce this issue on any app including the Example app. You mentioned that you’ve applied the patch on your instance already, now the question is, do you have minifying switch off on your instance from Admin=>site-configurations? Because only applying the patch at fw_base.js won’t help if your minified source is not update with my changes.
Please provide more information including JS console error.
Best regards,
Okay, I did that, nothing changed
Even upgraded to the latest maintenance version, but no luck. Still stalls the application. Pretty sure something is missing since the “Example” app also behaves the same way, all other apps work fine. By default on mobile it shows mail application.
Any other default app settings or permissions to check for on mobile, because it only stalls the app when it’s the default app in the next session on mobile