Socket Error in packet header 0

Any idea why when I try and run, using latest eclipse and sdk (not the beta) I get a Socket Error in packet header 0 and the simulator dies
  • Former Member
    Former Member
    Any idea why when I try and run, using latest eclipse and sdk (not the beta) I get a Socket Error in packet header 0 and the simulator dies


    Thank you for letting us know. We actually have a ticket that we are working on for this already and it should be fixed in the next SDK release. I have linked the ticket to this post. If your issues persist after the next SDK release, please let us know and we can reopen the issue. In your reply please be sure to give us any info that may be pertinent (OS, Eclipse Version, JAVA version, etc.) or send an email to [email][email protected][/email] with a link to this forum thread with the requested information.

    Thank you for your patience,

    -Coleman
  • city eastwood

    Thank you for letting us know. We actually have a ticket that we are working on for this already and it should be fixed in the next SDK release. I have linked the ticket to this post. If your issues persist after the next SDK release, please let us know and we can reopen the issue. In your reply please be sure to give us any info that may be pertinent (OS, Eclipse Version, JAVA version, etc.) or send an email to [email][email protected][/email] with a link to this forum thread with the requested information.

    Thank you for your patience,

    -Coleman


    Thats great but when will it be released? Currently I cannot develop BigTime and users are reporting issues do it it being built with older SDK.
  • Former Member
    Former Member
    Due to the nature of our release processes and the coordination needed with other teams around each release I am unable to give and ETA on the next release. Thank you for your patience.

    -Coleman
  • Is this affecting many loyal developers?
  • Former Member
    Former Member
    Is this affecting many loyal developers?


    This was found in house during our normal testing processes. There may have been others affected, but the report was internal. Please let us know if you continue to have issues after the release of the next SDK.

    -Coleman
  • This was found in house during our normal testing processes. There may have been others affected, but the report was internal. Please let us know if you continue to have issues after the release of the next SDK.

    -Coleman


    I'm seeing this regularly on 2.1.4

    Often the 2nd time I run the app in the simulator.