search

rubymotion-community / sugarcube

Some sugar for your cocoa. RubyMotion helpers.
Other
422 stars 66 forks source link

CGSize returned instead of CLLocationCoordinate2D under arm64 architecture #167

Closed kjf closed 10 years ago

kjf commented 10 years ago

When building and running a project with a basic sugarcube require under arm64, instantiating a new CLLocation instance and calling it's coordinates getter, a CGSize instance is returned instead of a CLLocationCoordinate2D instance.

Please see this project for an example: https://github.com/kjf/motion-cllocation-error

Seems to be working fine under arm7.

colinta commented 10 years ago

This is a rubymotion bug - can you report it with motion support?

colinta commented 10 years ago

(I was able to reproduce, btw, but there's nothing to fix in sugarcube)

kjf commented 10 years ago

I assumed that at first but it only seems to happen for me when I include sugarcube. If I remove the sugarcube dependency then then everything works as expected.

colinta commented 10 years ago

Oh! Interesting...

kjf commented 10 years ago

That's not to say it's not a rubymotion bug. It's just indirectly triggered via something sugarcube is doing.

I've skimmed the base sugarcube files and there's nothing obvious to me that sugarcube is doing that would cause this, it seems too low level for it to be so. Let me know if you think so too and I'll raise it via motion support.

colinta commented 10 years ago

Looks like it's not sugarcube after all, this recreates the issue for me:

https://gist.github.com/colinta/e8330099034f92d1977c

kjf commented 10 years ago

Cool, I'll open the issue with motion support.

kjf commented 10 years ago

Hey @colinta. Sorry for the hassle on this one but spending some more time on it today and I'm unable to make your example return the wrong type unless I explicitly have sugarcube compiled into the project.

If you take a look at: https://github.com/kjf/motion-cllocation-error/blob/master/Rakefile

When sugarcube is required the issue occurs. When it's not it doesn't. I'm still pretty convinced this is a RM issue but vanilla RM is definitely not causing it.

kjf commented 10 years ago

Ok scratch that. It seems like it happens regardless of what gem I require in my Rakefile, be it sugarcube, bubblewrap or whatever. I'll update the rubymotion support ticket. Sorry for the noise!