Hi,
We observe some strange behavior of client after disconnect() method call. If smartConnect is enabled, client always tries to connect via bluebox right after disconnect() call, even if socket connection can be used.
After some investigation we found that socketConnection.close() always (at ...
Search found 12 matches
- 30 Mar 2011, 15:43
- Forum: Java2SE / Android Client API
- Topic: Client tries to connect via bluebox after disconnect()
- Replies: 0
- Views: 22831
- 07 Dec 2010, 13:20
- Forum: Java2SE / Android Client API
- Topic: Annoying warnings while building Android apps
- Replies: 0
- Views: 22278
Annoying warnings while building Android apps
Hi,
dex tool from Android SDK emits a bunch of following warnings during application build process if application uses Java/Android SmartFox SDK:
warning: Ignoring InnerClasses attribute for an anonymous inner class that doesn't come with an associated EnclosingMethod attribute. (This class was ...
dex tool from Android SDK emits a bunch of following warnings during application build process if application uses Java/Android SmartFox SDK:
warning: Ignoring InnerClasses attribute for an anonymous inner class that doesn't come with an associated EnclosingMethod attribute. (This class was ...
- 23 Jul 2010, 18:33
- Forum: Java2SE / Android Client API
- Topic: Android 2.2 SDK is not work with Java Client API
- Replies: 10
- Views: 42181
- 01 Jul 2010, 08:37
- Forum: Java2SE / Android Client API
- Topic: Android 2.2 SDK is not work with Java Client API
- Replies: 10
- Views: 42181
- 10 Jun 2010, 08:29
- Forum: Java2SE / Android Client API
- Topic: Android 2.2 SDK is not work with Java Client API
- Replies: 10
- Views: 42181
- 15 Jul 2009, 07:32
- Forum: iPhone Objective-C API
- Topic: iPhone bugs
- Replies: 20
- Views: 81898
Hello!
Small bug in INFSmartFoxObjectSerializer.m in xml2obj:resObj: method: if received string is empty, it causes a problem at line 215, while trying to insert nil value into dictionary. I think that fix is simple - just check if varVal is nil and assign varValue an empty string instead of nil ...
Small bug in INFSmartFoxObjectSerializer.m in xml2obj:resObj: method: if received string is empty, it causes a problem at line 215, while trying to insert nil value into dictionary. I think that fix is simple - just check if varVal is nil and assign varValue an empty string instead of nil ...
- 14 Jul 2009, 08:51
- Forum: iPhone Objective-C API
- Topic: iPhone bugs
- Replies: 20
- Views: 81898
- 08 Jul 2009, 12:55
- Forum: iPhone Objective-C API
- Topic: iPhone bugs
- Replies: 20
- Views: 81898
- 10 Jun 2009, 08:00
- Forum: iPhone Objective-C API
- Topic: BlueBox support?
- Replies: 2
- Views: 26724
BlueBox support?
Hello!
As far as I can see, current version of iPhone API (beta2) does not support BlueBox, although its support is mentioned in documentation.
Is there any plan to add BlueBox support in near future?
Thanks.
As far as I can see, current version of iPhone API (beta2) does not support BlueBox, although its support is mentioned in documentation.
Is there any plan to add BlueBox support in near future?
Thanks.
- 15 May 2009, 14:27
- Forum: iPhone Objective-C API
- Topic: iPhone bugs
- Replies: 20
- Views: 81898
Thanks!Lapo wrote:New API available! -> http://forums.smartfoxserver.com/viewtopic.php?t=5106
- 06 May 2009, 15:30
- Forum: iPhone Objective-C API
- Topic: iPhone bugs
- Replies: 20
- Views: 81898
- 06 May 2009, 11:52
- Forum: iPhone Objective-C API
- Topic: iPhone bugs
- Replies: 20
- Views: 81898
Hello!
I think that there is a problem in stream:handleEvent:
(INFSmartFoxiPhoneClient.m line 453-...). I constantly get unhandled exception if server stops while my client is connected. In this case -1 is returned by read:maxLength: at line 529 and this case is not handled properly. This problem ...
I think that there is a problem in stream:handleEvent:
(INFSmartFoxiPhoneClient.m line 453-...). I constantly get unhandled exception if server stops while my client is connected. In this case -1 is returned by read:maxLength: at line 529 and this case is not handled properly. This problem ...