Any update about KM000035465 / OCTCR40D816086 ? - Android Push Notification failure

Audran Moulard 22 days ago

Any news on this problem ?

https://portal.microfocus.com/s/article/KM000035465?language=en_US

Known Problem OCTCR40D816086

Tags:

Mobile Management

Top Replies

Audran Moulard 16 days ago in reply to RaveNet +2

Mine was missing.
Audran Moulard 11 days ago in reply to Craig Wilson +2 verified

Works fine in 24.4
Craig Wilson 18 days ago in reply to Audran Moulard +1

I believe it is fixed in 24.4. Looking at the defect, 24.4 was the target, and requests were entered for official patches to be released for 23.4 and 24.2.

0 Craig Wilson 22 days ago

Still in Progress....

I think they have some test files....but most are waiting for an official release.

--

If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Be sure to "Like" My (and a few others) Cool Solutions below!

https://community.microfocus.com/members/craigdwilson/bookmarks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Audran Moulard 21 days ago in reply to Craig Wilson

We haven't had any contact with our Android devices for over a month now, and we can't enroll our Samsung A51, for example.
It's really a big problem for us.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Wilson 21 days ago in reply to Audran Moulard

I will see if I can get an ETA....Not sure if the release of 24.4 will speed it up....I know all available resources tend to get pulled into releases right before the ship....

--

If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Be sure to "Like" My (and a few others) Cool Solutions below!

https://community.microfocus.com/members/craigdwilson/bookmarks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Audran Moulard 18 days ago in reply to Craig Wilson

Is the issue still present in 24.4?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Wilson 18 days ago in reply to Audran Moulard

I believe it is fixed in 24.4.

Looking at the defect, 24.4 was the target, and requests were entered for official patches to be released for 23.4 and 24.2.

--

If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Be sure to "Like" My (and a few others) Cool Solutions below!

https://community.microfocus.com/members/craigdwilson/bookmarks
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RaveNet 17 days ago in reply to Craig Wilson

It's not resolved for me. I have ongoing ticket as 24.4 claims my new service json doesn't match.

Rodney

If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button. This helps others.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Wilson 17 days ago in reply to RaveNet

Sort of a Different issue.....24.4 has the updated APIs. The JSON issue just means a data file does not quite have the correct customer-specific data to communicate to the play store. I'm not saying it's user error as much the automated process of updating the files may not handle the data conversion in its creation seemlessly.

--

If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Be sure to "Like" My (and a few others) Cool Solutions below!

https://community.microfocus.com/members/craigdwilson/bookmarks
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Audran Moulard 16 days ago in reply to RaveNet

Mine was missing.
Cancel
Vote Up +2 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Wilson 15 days ago in reply to Audran Moulard

Thanks for the Update.......

--

If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Be sure to "Like" My (and a few others) Cool Solutions below!

https://community.microfocus.com/members/craigdwilson/bookmarks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RaveNet 15 days ago in reply to Audran Moulard

So, the issue is that we need to be using 'Firebase Cloud Messaging API V1, not legacy API.

Appears they forgot to document this change of api.

Switching new API on fixed my json error. Devices back in communication.

Rodney

If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button. This helps others.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Menu

ZENworks Configuration Management Discussions

Verified Answers

Any update about KM000035465 / OCTCR40D816086 ? - Android Push Notification failure

Tags:

Top Replies

Resources