If you have an iOS or windows device, worth try out. because sometime this could be platform/device specific. So we can narrow down the issue.
Thanks
Kapila
Hi;
If you have an iOS or windows device, worth try out. because sometime this could be platform/device specific. So we can narrow down the issue.
Thanks
Kapila
Hi @kathlk , neither for windows.
I already tested with the internet in house but no success.
Hi @lopespetro,
Can you check whether the custom events for push notifications in MaintEngApp are enabled in the IFS Application as below? If not, please enable those and check again. They are normally enabled once the MaintEngApp is in the Active state of the Applications screen.
@DAALLK - That will not help. Custom events used for trigger the push message. What’s happening here is device send push registration request to server and then server sends this to Azure Hub (Using HUB settings in app params). If that fails (Wrong hub settings) then you do not see this push enabled check box. If your device does not enable the push notifications in Os level for the app, then device does not sends this registration request and you can see the similar behaviour. In android you can check it via settings I guess.
Next option is to check device logs in android. May be you can send/email device logs. It will show any errors during the push registration.
Another possibility is a bug in this app binary => 10.13.1360.0 where it does not have right Push settings packaged. Worth activate same app in different environment.
Hi @lopespetro,
Can you check whether the custom events for push notifications in MaintEngApp are enabled in the IFS Application as below? If not, please enable those and check again. They are normally enabled once the MaintEngApp is in the Active state of the Applications screen.
Hi @Dharshika Amaradasa, Yes, it’s checked.
Tks for attention.
@DAALLK - That will not help. Custom events used for trigger the push message. What’s happening here is device send push registration request to server and then server sends this to Azure Hub (Using HUB settings in app params). If that fails (Wrong hub settings) then you do not see this push enabled check box. If your device does not enable the push notifications in Os level for the app, then device does not sends this registration request and you can see the similar behaviour. In android you can check it via settings I guess.
Next option is to check device logs in android. May be you can send/email device logs. It will show any errors during the push registration.
Another possibility is a bug in this app binary => 10.13.1360.0 where it does not have right Push settings packaged. Worth activate same app in different environment.
Hi @kathlk, tks for the explanation.
One thing I have noticed is also the message in logs:
In app device the notification is alloweded.
I’ll check the client log.
Tks
Hi everyone!
the local support has resolved the issue just by setting up the user in TAS config.
At first, changing to the owner user worked right.