09-13-2011 04:30 AM
hi i try to add NFC listener to app but i always get exception "Listener belongs to another application module"
what that mean? i already check that nothing module contain NFC listener
Solved! Go to Solution.
09-26-2011 09:01 AM
I have not looked at NFC Listener (yet) but I assume it is like other Listeners, it runs in the 'owning' application, like the Phone Listeners run in the Phone application. In these cases you need to ship the data to your own application, and the preferred way to do that is using Global Events.
What processing were you actually trying to do in the Listener that provoked this Exception?
As noted, I have not looked, perhaps this is completely tosh, if so I'm sorry, I'm just trying to help....
09-27-2011 10:24 AM
I've exactly the same problem...
It occurs when I set 3 or more Entry point but not when I've only 2.
I register the listener only when I launch my nfc entrypoint (I've added nfc as parameter) but I've got this error.
This error occurs only on the device even if I launch only the nfc entrypoint.
When I remove all other entrypoint everything works fine.
How can you explain that? My main application (the first defined in descriptor.xml) is my NFC entrypoint so, why did it said me that?
09-28-2011 10:23 AM
09-28-2011 10:41 PM
i think its not a solution for the problem, but this is in my case:
i join my NFC listener (NDEFMessageListener) and screen, so i set NFC listerner in my constructor screen it always throw an exception.
so i change to not to set listener in constructor, but i make a function to set the listener : example
it work well, but i just for NDEF message listernet, it i use target listener it will throw same exception
10-14-2011 10:46 AM
I think people may have hit an issue known to affect the TransactionListener from the NFC API. I hadn't heard of it for other NFC listeners however. Here's the problem we know about for TransactionListener:
If your application gets split into multiple sibling cod files then you may get this issue. The workaround is to have your main application class (sub-class of UiApplication or Application) implement the interface. This should stop you seeing this error.
I believe the issue is fixed in later 7.0 builds.
If people still have problems after trying this suggestion please post:
- whether or not you have sibling cod files
- whether you see the problem on a real device or simulator
- in either case, which device and what API/OS build you are running with.
10-17-2011 04:39 AM - edited 11-17-2011 11:00 AM
Having checked this further, I can report that for 9900 (Bold) devices the issue should be fixed in OS version 22.214.171.1247 (bundle 1603) whilst for 9360 (Curve) it should be fixed at 126.96.36.1990 (bundle 1699).
If you do hit this problem therefore, you should upgrade devices to this version at a minimum and re-test.
10-18-2011 10:45 PM
I testing a small MIDlet on Blackberry Curve 9360 which only registers the TransactionListener to detect if a transaction has been made. I am encountering the ControlledAccessException as soon as I register the listener.
How can I overcome this exception? Is there anyway other than upgrading the firmware?
There is no multiple cods created
The device is running on v188.8.131.52
10-19-2011 03:21 AM
Is your MIDlet signed with the NFCR signing key?