forums.smartfoxserver.com

Hi,

Google is migrating its Google Mobile Ads SDK from Admob to Google Play Services. When converting our Android multiplayer app to Google Play Services, SmartFox simple can't connect anymore with the error:

04-08 15:35:35.099: W/System.err(14036): 13131 [New I/O client worker #1-1] WARN sfs2x.client.controllers.SystemController - No handler exists for this event: 0

It is very easy to reproduce the problem:

1) Download install and run the SmartFox Server on your machine (with the latest patch applied)
2) Download the Android SimpleChat example app and update the SmartFox Client API jars
3) Run the app and connect with the server running on your machine. The app will work flawlessly, as expected
4) Follow these instructions to integrate the Google Mobile Ads SDK:
https://developers.google.com/mobile-ads-sdk/docs/
https://developer.android.com/google/pl ... setup.html
5) Add a simple banner (on the XML) of the sample app
6) The app does not connect anymore

It was tested with the latest Android ADT and SDK in a Samsung Galaxy S2 with Android 4.1.2. I can send the SimpleChat example with the banner integrated if necessary.

This is a very serious problem because as of August 1, 2014 Google will not accept apps with the Admob implementation (only Google Play Service implementation).

Best regards,
Akira

Thanks for reporting. We didn't know about this.
If you could send the example application you are using it would be great.

You can zip it and send it to our support@... email with a reference to this post. Or upload it to a free service and send us a link

Thanks

Hi Lapo,

I've just sent an email with the projects files used to reproduce the problem.

Best regards,
Akira

Thank you, mail received.
We'll take a look and let you know.

Hi

I have the same problem. Are there any solutions?

Thanks

Hi,
to be honest this was not a real problem. We exchanged a number of emails where we could not reproduce the error but the client still was having all sorts of weird error.

It turned out that there were multiple problems with the client's setup: mixed jar files from multiple distributions of our API and problems with Eclipse.

Finally he setup Android Studio on another machine, downloaded our API from the website and the problem disappeared.

Maybe you're facing a similar issue?