Issue regarding custom application loading on mobile

RalfBecker · Sep '21

There’s nothing we can do with the amount of information you gave

Googling for Promise rejection NotAllowed Error gives some pointers, you could check with your applications code: https://www.google.com/search?q=promise+rejections+NotAllowedError&oq=promise+rejections+NotAllowedError&aqs=chrome..69i57.9583j0j7&sourceid=chrome&ie=UTF-82

Browsers reject a lot of things:

mixed content (http sources in a top-level https page)
our Content Security Policy allows only certain JS actions and resources on the page
cross-origin requests

I can only speculate without knowing what your application does and its code.

Ralf

vishakha · Sep '21

Is there anything special that needs to be done for setting default application on mobile in the code ?

vishakha · Sep '21

$GLOBALS['egw_info']['flags'] = array(
		'currentapp'              => 'myapp',
		'noheader'                => True,
		'nonavbar'                => True,
		'enable_nextmatchs_class' => True
	);
include('../header.inc.php');

Api\Egw::redirect_link('/index.php','menuaction=myapp.uimyapp.index');

This is my index.php of custom app, if it helps.

RalfBecker · Sep '21

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

vishakha · Sep '21

	$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 ?

RalfBecker · Sep '21

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

vishakha · Sep '21

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.

RalfBecker · Sep '21

Try again with Chrome switching to a mobile profile. Maybe you get lucky and get a better error-message …

Ralf

vishakha · Sep '21

Does this make any sense ?

StefanU · Sep '21

You cannot read this screenshot. Please paste the screenshot in full size.
Stefan

vishakha · Sep '21

Screenshot from 2021-09-21 15-53-06.png1743x953 217 KB

RalfBecker · Sep '21

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

RalfBecker · Sep '21

Nope that function is in fw_desktop.js:

github.com

EGroupware/egroupware/blob/master/api/js/framework/fw_desktop.js#L523


		{
			var tab = this.tabsUi.getTab(_appname);
			// do not set tab's notification if it's the active tab
			if (tab && (this.activeApp.appName != _appname || _value == 0))
			{
				this.tabsUi.getTab(_appname).setNotification(_value);
			}
		},


		/**

		 * This method only used for status app when it tries to broadcast data to users

		 * avoiding throwing exceptions for users whom might have no status app access

		 *

		 * @param {type} _data

		 * @returns {undefined}

		 */
		execPushBroadcastAppStatus: function(_data)

		{
			if (app.status) app.status.mergeContent(_data, true);
		},

But the fw_mobile.js does not have that method:

github.com

EGroupware/egroupware/blob/master/pixelegg/js/fw_mobile.js#L314


			//As we can not calculate the delta value, add 30 px as delta
			this.$iFrame.css({width:_width+30,	height:_height+30});
		}
	});


	/**

	 * mobile framework object defenition

	 * here we can add framework methods and also override fw_base methods if it is neccessary

	 * @type @exp;fw_base@call;extend

	 */
	var fw_mobile = fw_base.extend({


		// List of applications available on mobile devices
		DEFAULT_MOBILE_APP : ['calendar','infolog','timesheet','resources','addressbook','projectmanager','tracker','mail','filemanager'],


		/**

		 * Mobile framework constructor

		 *

		 * @param {string} _sidemenuId sidebar menu div id

		 * @param {string} _tabsId tab area div id

		 * @param {string} _webserverUrl specifies the egroupware root url

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

RalfBecker · Sep '21

Hadi moved the method to the base-class:

This will be part of the maintenace planned for today or tomorrow.

Ralf

vishakha · Sep '21

It’s the archive installation and I have the status app installed

vishakha · Sep '21

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

RalfBecker · Sep '21

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

vishakha · Sep '21

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

vishakha · Sep '21

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.

hadi.nategh · Sep '21

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,

share a link to this topic