Search found 25 matches
- 02 May 2021, 15:17
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: Disconnection issues on iOS
- Replies: 21
- Views: 36239
Re: Disconnection issues on iOS
Hi milesstone, How do you do that?
- 28 Dec 2020, 18:53
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: iOS| Disconnection during app in background
- Replies: 4
- Views: 14438
Re: iOS| Disconnection during app in background
It doesn't help. once the screen turns off the OS probably close all the sockets excepts for VOIP.
- 22 Dec 2020, 14:05
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: iOS| Disconnection during app in background
- Replies: 4
- Views: 14438
Re: iOS| Disconnection during app in background
Thanks for the quick response, I will try it!
- 22 Dec 2020, 08:58
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: iOS| Disconnection during app in background
- Replies: 4
- Views: 14438
iOS| Disconnection during app in background
Hi My iOS clients suffer from connection loss when going to the background for a few seconds. (iOS probably kill the TCP socket?) I wanted to ask for your suggestion on how can I overcome the iOS disconnections because my game is not tolerant of those disconnections. When the connection drop, I can'...
- 20 Dec 2020, 18:45
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
Seems strange.
Was the exception triggered before or after the reconnection?
It happens when we come back from the background. I can see that onConnectionRetry was called, but onConnectionResume wasn't.
- 17 Dec 2020, 12:27
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
I agree with you, but you can implement the default callback to send a custom exception, and give the ability to override this callback as well. I don't think this is doable, without breaking compatibility with previous API versions. The way you delegate callbacks is by passing an implementation of...
- 16 Dec 2020, 15:40
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
I don't think that throw a general exception is the best way to handle it. we will be glad if it will be done via your callbacks, then we will disconnect and do the necessary stuff.
BTW, this situation can also occur in JAVA as well?
BTW, this situation can also occur in JAVA as well?
- 16 Dec 2020, 10:03
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
Can't you call a new callback let's say onConnectionFatalError, instead of throwing an exception?
BTW, at this point, can you send detailed info? errno? stuff like that
BTW, at this point, can you send detailed info? errno? stuff like that
- 15 Dec 2020, 08:15
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
Fatal Exception: NSRangeException *** -[NSConcreteMutableData getBytes:range:]: range {140, 128} exceeds data length 143 Fatal Exception: NSRangeException 0 CoreFoundation 0x192482114 __exceptionPreprocess 1 libobjc.A.dylib 0x1a5d1ecb4 objc_exception_throw 2 Foundation 0x19365cb48 -[NSString hash] ...
- 14 Dec 2020, 16:56
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
Thanks for the detailed answer. Let's say I will catch all of the uncached exceptions in my app, I don't think Crashlyics will like that. Let's say they will like it :), then how should I know where this exception came from? NSRangeException can be raised from many methods, there is another way to c...
- 14 Dec 2020, 11:55
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
What should I do with this exception? I expect Crashlytics to catch this exception anyway.
But let's say I will catch it manually, will SF continue to work or the connection is broken? if yes, I would expect you to catch it and call to onServerConnetionLost with unknown reason
But let's say I will catch it manually, will SF continue to work or the connection is broken? if yes, I would expect you to catch it and call to onServerConnetionLost with unknown reason
- 13 Dec 2020, 14:43
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
Sorry for the long delay. I'm using Crashlytics for collecting all exceptions and crash in my app. I will open a ticket for Crashlytics about why they crash. But beforehand, why your code doesn't handle this exception internally? Is this situation for throwing such an exception from your side is acc...
- 01 Dec 2020, 09:24
- Forum: SFS2X Questions
- Topic: HRC feature
- Replies: 3
- Views: 5850
Re: HRC feature
But we use a TCP connection, in that case, you should enqueue the failed message and resend it when it reconnects, right? We have a stage in our game that every message must be received, if we don't receive all the messages in the exact order we get stuck. We can develop a mechanism of asking for a ...
- 29 Nov 2020, 09:26
- Forum: SFS2X Questions
- Topic: HRC feature
- Replies: 3
- Views: 5850
HRC feature
Hi Recently we enabled HRC feature in our production environment in order to overcome some momentary disconnections. Let's say we send messages (TCP) 11 12 13 14 to our clients and one of the clients encounters an issue just before sending a message no. 13. I observe that after reconnecting the clie...
- 16 Sep 2020, 14:44
- Forum: SFS2X iPhone / iPad / OSX API
- Topic: internal crash when parsing a message
- Replies: 23
- Views: 27474
Re: internal crash when parsing a message
But should it crash?