08-11-2011 09:29 AM
I'm trying to send Email from FolderListener , it is giving Exception on Device PlatformVersion: 184.108.40.206 Device OS: 220.127.116.116 DeviceModel: 9800 , while running fine on Device PlatformVersion: 18.104.22.168 Device OS: 22.214.171.1248 DeviceModel: 9700 & Device PlatformVersion: 126.96.36.199 Device OS: 188.8.131.524 DeviceModel: 9700.
How can I overcome this issue?
Solved! Go to Solution.
08-11-2011 09:34 AM
08-11-2011 01:04 PM
Thanks for reply simon, I have tried it with Global Event too,still its giving same Exception.
08-11-2011 08:04 PM
What Simon means is that you trigger a Global Event in the listener, listen for this Event in your application, and run the email generating code in your application.
Prior to doing this, you might like to just test that your application can send an email.
From what I know, RIM have been working to tighten up they listener code because a listener runs in the Application that it is listening too, which is possibly not wise. So perhaps you have hit something related to this, which running in your own Application will overcome.
Alternatively you may have just hit a bug.
Regardless, using a GlobalEvent is better than trying to do this in the folder listener.
08-12-2011 12:35 AM
I have tried exactly what you are saying.I have registered GlobalEventListener in my application and triggered Event from FolderListener still its giving "Unauthorized attempt to attach to this application".
08-12-2011 03:36 AM
And can your application send an email without the Event Trigger?
08-12-2011 05:03 AM
yes peter, my application is sending mail from other places which are not triggred by FolderListener.
08-12-2011 05:09 AM
OK, I honestly can't see why you should not be able to send from your GlobalEventListener. Looks like a bug.
Can I suggest you create a simple Application that does just enough to demonstrate the problem(i.e. adds the Listener, generates a globalEvent, processes the global Event in your own application, but also allows the user to send an email) and replicate the problem with that. Then you can use Incident Tracker to report the problem. In the mean time you could also post the code here, I suspect others have similar processing and will be happy to see if they have the same problem and so support your incident.
08-12-2011 09:09 AM
Its creating problem only on OS: 184.108.40.2066 even working fine on Other 4.6 to 6.0 versions I have with or without GlobalEvent.