Tuesday, 17 July 2012

Aaaargh...we screwed up the latest n-Mobility DEMO version...

We introduced a really nasty bug in version 2.5.4 of our n-Mobility Demo (FREE) client. We had good intentions to increase the number of databases and views within each database that can be configured and used with the free client, but messed it up (the full version is not effected by this issue).

After installing the n-Mobility Demo client one would immediately get an error screen with following (or similar) message...


RangeError: Index '4' specified is out of bounds.
at mx.collections::ListCollectionView/getItemAt()[E:\dev\4.y\frameworks\projects\framework\src\mx\collections\ListCollectionView.as:502]
at mx.collections::ListCollectionView/http://www.adobe.com/2006/actionscript/flash/proxy::getProperty()[E:\dev\4.y\frameworks\projects\framework\src\mx\collections\ListCollectionView.as:874]
at views::MobileNotesWorkspace/receivedDatabaseList()[C:\FBW\nMobility\src\scripts\MobileNotesWorkspace.as:301]
at packages.DominoUtilities::DominoDBUtilities/common_arraycol2d_result()[C:\FBW\Flex4Soapgate\src\packages\DominoUtilities\DominoDBUtilities.as:1800]
at packages.DominoUtilities::DominoDBUtilities/dbcolumnx_result()[C:\FBW\Flex4Soapgate\src\packages\DominoUtilities\DominoDBUtilities.as:1514]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AbstractOperation.as:249]
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:318]
at mx.rpc::Responder/result()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\Responder.as:56]
at mx.rpc::AsyncRequest/acknowledge()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:84]
at DirectHTTPMessageResponder/completeHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\DirectHTTPChannel.as:451]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()

The reason for this error is that the client is expecting at least (not up to) 5 databases (the same applies to the number of views), though it would show only the first 5 anyway. Until today only 4 databases had been configured in our Flexdomino.net test environment to which the client connects to by default. And hence the above "Out of Bounce" error.

We have fixed this temporarily by making sure our test environment has 5 demo databases and at least 5 views within each database. If you want (or have already tried) to use the n-Mobility client in your environment, you must ensure that the soapgate Q! database on your server contains at least 5 active Database Access Profiles and each profile contains 5 at least 5 views.

As said above, only the demo (or free) version 2.5.4 of the n-Mobility client is effected.

If you have already installed the n-Mobility client 2.5.4 and received the above error message, please open the Setup screen inside the app and use the Reset System feature (under Local Cache Maintenance) to set your application back to default settings (effectively clearing any locally cached data).

After that you can test the free app again with our demo databases on Flexdomino.net without problems.

A fixed update of the n-Mobility Demo client will be posted on the respective app stores asap.

We apologise for the inconvenience.

The Flexdomino.net Team

No comments:

Post a Comment