Discussions regarding 1C:Enterprise for mobile devices with Android, iOS, or Windows Phone.

#1
People who like this: 0 Yes / 0 No
Just came
Rating: 1
Joined: Jul 8, 2015
Company:

Dear Community,

It would be very helpful if someone could provide clarity on the functioning of FCM push notifications in 1c mobile apps.

Our mobile 1c app is compiled into an apk file via 1c Mobile App Builder and then installed on an Android device. Mobile platform used is 8.3.15.86. We use pushnotifications.1c.com service to deliver
FCM push notifications from an 1c infobase to this mobile app. Notifications are received and handler does what it has to do - desired programmed actions are automatically taken in the app.

We intent to send same notifications from an external/non-1c system, so attempted to test it by sending requests (Body > raw > format JSON. method POST. endpoint 'https://fcm.googleapis.com/fcm/send') from POSTMAN and bat file first, but only with "half" success - via POSTMAN or bat file the notification is received on the device, then notification is pushed, app opens, but handler doesn't seem to work, same programmed actions are not triggered/taken in the app.
Unable to get it to work for some time now. Maybe if the source of the notification is not 1C based it just will not work and that is it? Or maybe there are very specific requirements for the request that we do not satisfy?

Best Regards,
Ged

 
#2
People who like this: 0 Yes / 0 No
Just came
Rating: 1
Joined: Jul 8, 2015
Company:

We managed to figure it out. JSON example below worked/solved it for us.

{
   "to": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
   "data": {
       "title": "test",
       "data": "1",
       "text": "test",
       "base": ""
   }
}

 
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)
Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.

/* --- ФИКС ЗАГОЛОВКОВ ДОКУМЕНТАЦИИ (BRUTE FORCE) --- */ /* Цепляемся за все возможные контейнеры Битрикса */ .content h1, #content h1, .workarea h1, .content h2, #content h2, .workarea h2, .content h3, #content h3, .workarea h3, .content h4, #content h4, .workarea h4, .content h5, #content h5, .workarea h5, .content h6, #content h6, .workarea h6 { display: block !important; font-weight: 700 !important; color: #222 !important; text-transform: none !important; margin-top: 1.5em !important; margin-bottom: 0.5em !important; line-height: 1.2 !important; } /* Явно задаем размеры, чтобы перекрыть "font-size: 100%" */ .content h1, #content h1 { font-size: 28px !important; } .content h2, #content h2 { font-size: 24px !important; } .content h3, #content h3 { font-size: 22px !important; } .content h4, #content h4 { font-size: 20px !important; } .content h5, #content h5 { font-size: 18px !important; } /* Ваш случай (5 решеток) */ .content h6, #content h6 { font-size: 16px !important; } /* Если Битрикс или редактор засунули внутрь h5 тег span или font */ .content h5 *, #content h5 *, .workarea h5 * { font-size: inherit !important; color: inherit !important; font-weight: inherit !important; } /* --- СТИЛИЗАЦИЯ ТЕКСТА (Markdown Style) --- */ /* Ссылки в тексте делаем более заметными */ .content a:not([class]) { color: #005aa0; text-decoration: none; border-bottom: 1px solid rgba(0, 90, 160, 0.2); } .content a:not([class]):hover { border-bottom-color: #005aa0; } /* Списки (чтобы не прилипали) */ .content ul, .content ol { margin-bottom: 15px !important; padding-left: 20px !important; } .content li { margin-bottom: 5px !important; }