Issue regarding custom application loading on mobile

vishakha 2021-09-17 15:36:20 UTC #1

Using latest version 21.1
Apache server
PHP 7.4
mariadb
archive installation

Hi, I’m having an issue on mobile with custom application. The first time I logged in and selected the custom app it worked perfectly on mobile. When logged in the second time because now it is selected as the default application and loaded in the cache, the application wouldn’t load and it just freezes

StefanU 2021-09-17 16:24:07 UTC #2

Hi Vishakha.

Can you find anything in the web server (error) log?

I have moved this to the Developer category…

Stefan

vishakha 2021-09-17 17:19:38 UTC #3

I don’t see anything in the error logs

StefanU 2021-09-17 17:35:29 UTC #4

And desktop webbrowser => Developer tools / Console with mobile client view?
Stefan

vishakha 2021-09-17 17:55:00 UTC #5

vishakha 2021-09-20 19:32:34 UTC #6

Just checking if there’s anything that needs to be done from our side for the above issue

RalfBecker 2021-09-21 06:09:24 UTC #7

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-8

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 2021-09-21 15:13:47 UTC #8

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

vishakha 2021-09-21 15:43:23 UTC #9

$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 2021-09-21 15:46:24 UTC #10

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 2021-09-21 16:12:56 UTC #11

	$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 2021-09-21 16:43:31 UTC #12

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 2021-09-21 16:46:03 UTC #13

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 2021-09-21 17:57:32 UTC #14

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

Ralf

vishakha 2021-09-21 18:35:17 UTC #15

Does this make any sense ?

StefanU 2021-09-21 19:21:02 UTC #16

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

vishakha 2021-09-21 19:59:04 UTC #17

RalfBecker 2021-09-22 06:31:34 UTC #18

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 2021-09-22 06:51:32 UTC #19

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 2021-09-22 11:53:52 UTC #20

Hadi moved the method to the base-class:

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

Ralf