Skip to content
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

inScope:JSObjectionScopeSingleton doesn't work since Cocoapods version 1.6 #94

Closed
pual opened this issue Jul 18, 2015 · 19 comments
Closed

Comments

@pual
Copy link

pual commented Jul 18, 2015

I'm using the singleton registration ([self bindClass:... inScope:JSObjectionScopeSingleton];) in a JSObjectionModule in my app for quite a while.
After a pod update to version 1.6 the singleton scope is ignored and handled like JSObjectionScopeNormal.

@mpurland
Copy link
Contributor

+1

@jdewind
Copy link
Contributor

jdewind commented Jul 22, 2015

Odd,

I'll look into it today.

@jdewind
Copy link
Contributor

jdewind commented Jul 22, 2015

I'm unable to reproduce the issue and I do have a test that exercises the "inScope" registration.

See https://github.com/atomicobject/objection/blob/develop/Specs/ModuleUsageSpecs.m#L172.

I'll need to have a code example to investigate further at this point. Also, its important that there aren't multiple revisions of Objection running within the project -- that can cause these kind of strange issues.

@zintus
Copy link

zintus commented Jul 29, 2015

My quick investigation shown, that problem lies in absence of synthesize statement for lifeCycle property in JSObjectionProviderEntry.m file. This leads to usage of property getter defined in base class (JSObjectionEntry.m), always returning JSObjectionScopeNone.

@jdewind
Copy link
Contributor

jdewind commented Jul 29, 2015

Good catch. I'm disappointed that the tests are unable to reproduce it.

@zintus
Copy link

zintus commented Jul 29, 2015

I'm happy to help!

@plu
Copy link
Contributor

plu commented Jul 30, 2015

I'd help too, but I'm not sure what's the current state of the repo. If I try to run the test suites on Xcode 6.4, it doesn't even build. When I update Quick and Nimble submodules to latest master, it works. But then some tests are failing.

@jdewind
Copy link
Contributor

jdewind commented Jul 30, 2015

@plu Its running in travis and all tests are passing. I believe it is using the same version of XCode as well.

@plu
Copy link
Contributor

plu commented Jul 30, 2015

@dewind I don't think so. It's using Xcode 6.1:

https://travis-ci.org/atomicobject/objection/builds/73209281

Xcode 6.1
Build version 6A1052c

You need to click on announce right next to $ xcodebuild -version -sdk to see the full output.

It's definitely broken on 6.4. What's your local setup? :)

But of course I just might be missing something here :)

@jdewind
Copy link
Contributor

jdewind commented Jul 30, 2015

@plu Similar to Travis CI. I'll need to get on a machine with 6.4 and address those issues ASAP. I'll open a new issue.

@plu
Copy link
Contributor

plu commented Jul 30, 2015

Cool thanks! I can have a look at them too right now.

@plu
Copy link
Contributor

plu commented Aug 27, 2015

What about cutting a new release 1.7? :)

@scottkilker
Copy link

Any updates on this issue?

@zintus
Copy link

zintus commented Oct 12, 2015

Up

@jdewind
Copy link
Contributor

jdewind commented Oct 12, 2015

Sorry guys,

I'll review the issue this week.

@zintus
Copy link

zintus commented Dec 8, 2015

@dewind gentle bump :)

@CapnSpellcheck
Copy link

This made it into 1.6.1 did it not? https://github.com/atomicobject/objection/releases/tag/1.6.1

@zintus
Copy link

zintus commented Dec 12, 2015

Oh, I'm sorry 😬

Let's close issue then?

@pual
Copy link
Author

pual commented Dec 14, 2015

Yes, it works now, thanks!

@pual pual closed this as completed Dec 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants