-
-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with iOS #46
Comments
Thanks for reporting this! Could you possibly create a minimal xcode project that reproduces this issue in an iOS build? cheers
|
Out of curiousity, is your project multithreaded? |
Have isolated the issue to be with Unity using the library. Will update when things are figured out. Yes, project is multi-threaded, but accesses libyojimbo in safe manner. |
OK sounds good. Let me know what you find! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Able to build on iOS but run into runtime issues.
Run into memory access issues (
EXC_BAD_ACCESS
) involving the allocator/deallocator macros, e.g.Stack trace:
From debugger:
In a hack, replaced the allocator macros with just plain
new
anddelete
which seems to get around theEXC_BAD_ACCESS
issue, but clients are unable to establish connections with the server.The code works on Mac (x86_64), Linux (x86_64) and Windows (x86_64).
The text was updated successfully, but these errors were encountered: