Welcome!

Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
All New Topics | All New Posts
inside custom component

BlackBerry Mobile Fusion

Reply
Topic Options
conito68
Contributor
conito68
Posts: 19
Registered: ‎10-12-2010

Communication Logs: action.eassync failure

Options

‎12-13-2012 10:09 AM

Has anyone come across this in their communication logs?  There's no information on it on the BlackBerry support site, and I've never run across it before.

 

action.eassync      failure

 

I've got a single user who I can't push the EAS profile to. iPhone 5 CDMA/LTE.  All other profiles get pushed to the user properly. 

 

Running latest version of UDS.

Report Inappropriate Content
Message 1 of 8 (1,910 Views)
Reply
0 Likes
Please use plain text.
 
martinpas
Contributor
martinpas
Posts: 22
Registered: ‎10-03-2011
My Carrier: Claro

Re: Communication Logs: action.eassync failure

Options

‎12-28-2012 12:55 PM

Same problem, any idea?

 

Anybody?

 

 

Report Inappropriate Content
Message 2 of 8 (1,711 Views)
Reply
0 Likes
Please use plain text.
 
BlackBerry Technical Advisor
BlackBerry Technical Advisor
-BD-
Posts: 333
Registered: ‎05-15-2008
My Carrier: Rogers

Re: Communication Logs: action.eassync failure

Options

‎12-30-2012 01:34 AM

What version is the iphone at?

Report Inappropriate Content
Message 3 of 8 (1,719 Views)
Reply
0 Likes
Please use plain text.
 
martinpas
Contributor
martinpas
Posts: 22
Registered: ‎10-03-2011
My Carrier: Claro

Re: Communication Logs: action.eassync failure

Options

‎12-30-2012 01:39 AM

I had the same issue with android 2.3

Report Inappropriate Content
Message 4 of 8 (1,691 Views)
Reply
0 Likes
Please use plain text.
 
conito68
Contributor
conito68
Posts: 19
Registered: ‎10-12-2010

Re: Communication Logs: action.eassync failure

Options

‎12-31-2012 02:11 PM

In my situation it was 6.0.1

Report Inappropriate Content
Message 5 of 8 (1,668 Views)
Reply
0 Likes
Please use plain text.
 
julieliddell
New Contributor
julieliddell
Posts: 2
Registered: ‎03-05-2013
My Carrier: Rogers

Re: Communication Logs: action.eassync failure

[ Edited ]
Options

‎03-05-2013 10:45 AM - edited ‎03-05-2013 10:48 AM

same error here - i phone 4S

OS if 6.1 - carrier is Sprint.  UDS is at the latest level and we haven't seen this on the ipads using the same OS

Report Inappropriate Content
Message 6 of 8 (1,061 Views)
Reply
0 Likes
Please use plain text.
 
moorken
Visitor
moorken
Posts: 1
Registered: ‎03-22-2013
My Carrier: Proximus

Re: Communication Logs: action.eassync failure

Options

‎03-22-2013 08:34 AM

we have 100% the same problem, iphone 4S, OS 6.1

maart 22, 2013 1:33:58 PM (CET): command.application success
maart 22, 2013 1:33:57 PM (CET): command.deviceinfo success
maart 22, 2013 1:33:50 PM (CET): action.poke success
maart 22, 2013 1:33:50 PM (CET): command.application request
maart 22, 2013 1:33:50 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 1:33:50 PM (CET): command.deviceinfo request
maart 22, 2013 1:18:46 PM (CET): command.application success
maart 22, 2013 1:18:45 PM (CET): command.deviceinfo success
maart 22, 2013 1:18:38 PM (CET): action.poke success
maart 22, 2013 1:18:38 PM (CET): command.application request
maart 22, 2013 1:18:38 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 1:18:38 PM (CET): command.deviceinfo request
maart 22, 2013 1:03:35 PM (CET): action.poke success
maart 22, 2013 1:03:35 PM (CET): command.application request
maart 22, 2013 1:03:35 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 1:03:35 PM (CET): command.deviceinfo request
maart 22, 2013 1:03:35 PM (CET): action.breach success
maart 22, 2013 12:50:19 PM (CET): action.eassync failure
maart 22, 2013 12:48:28 PM (CET): command.application success
maart 22, 2013 12:48:26 PM (CET): command.deviceinfo success
maart 22, 2013 12:48:26 PM (CET): action.eassync request
maart 22, 2013 12:48:25 PM (CET): action.poke success
maart 22, 2013 12:48:23 PM (CET): action.poke success
maart 22, 2013 12:48:20 PM (CET): action.poke success
maart 22, 2013 12:48:20 PM (CET): command.application request
maart 22, 2013 12:48:20 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 12:48:20 PM (CET): command.deviceinfo request
Report Inappropriate Content
Message 7 of 8 (920 Views)
Reply
0 Likes
Please use plain text.
 
julieliddell
New Contributor
julieliddell
Posts: 2
Registered: ‎03-05-2013
My Carrier: Rogers

Re: Communication Logs: action.eassync failure

Options

‎04-05-2013 10:52 AM

Exact same for all Non-BB device users oin our UDS however all are receiving their email so I'm not sure what to make of it.

April 5, 2013 10:49:11 AM (EDT):command.applicationsuccess
April 5, 2013 10:48:52 AM (EDT):action.pokesuccess
April 5, 2013 10:48:52 AM (EDT):command.applicationrequest
April 5, 2013 10:46:18 AM (EDT):command.deviceinfosuccess
April 5, 2013 10:46:12 AM (EDT):action.pokesuccess
April 5, 2013 10:46:12 AM (EDT):command.deviceinfo_bdmirequest
April 5, 2013 10:46:12 AM (EDT):command.deviceinforequest
April 5, 2013 10:40:13 AM (EDT):action.eassyncfailure
April 5, 2013 10:38:48 AM (EDT):command.applicationsuccess
April 5, 2013 10:37:51 AM (EDT):action.pokesuccess
April 5, 2013 10:37:51 AM (EDT):command.applicationrequest
April 5, 2013 10:36:08 AM (EDT):command.deviceinfosuccess
April 5, 2013 10:36:00 AM (EDT):action.pokesuccess
April 5, 2013 10:36:00 AM (EDT):command.deviceinfo_bdmirequest
April 5, 2013 10:36:00 AM (EDT):command.deviceinforequest
April 5, 2013 10:27:49 AM (EDT):command.applicationsuccess
April 5, 2013 10:27:19 AM (EDT):action.pokesuccess
Report Inappropriate Content
Message 8 of 8 (776 Views)
Reply
0 Likes
Please use plain text.