Skip to content

Localization is broken since Parse 1.8 #42

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

Closed
wouterds opened this issue Aug 18, 2015 · 8 comments
Closed

Localization is broken since Parse 1.8 #42

wouterds opened this issue Aug 18, 2015 · 8 comments
Labels
state:duplicate Duplicate of already reported issue

Comments

@wouterds
Copy link

What happened guys? Where are all the previous versions? What's the reason all the previous releases were deleted?

Because there's only 1.8 everyone upgraded to the latest version and everyone seems to be fucked. This version is breaking Localization and there's no way to downgrade (using Cocoapods, doesn't take any older versions anymore, always 1.8).

Edit: removed all the rage & added a bit more info.

@wouterds
Copy link
Author

Apparently a duplicate of #16

@wouterds
Copy link
Author

Never the less, still interested why older releases were deleted.

@wouterds
Copy link
Author

Apparently because of license issues since the opensourcing of the SDK the previous versions are no longer available I just read somewhere. To answer my own question.

Full story about the opensourcing of the SDKs: http://blog.parse.com/announcements/open-sourcing-our-sdks/

@nlutsenko
Copy link
Contributor

Old versions of the SDK are still available through Cocoapods and website downloads.
Not aware about the licensing issues, but the answer to the question on why didn't we open source previous versions as well - because it's not really useful to use old things.
We are working hard to fix any issue in a matter of days if not hours, so rolling forward (using the latest) is preferred to rolling backward (using the previous).

@nlutsenko nlutsenko added the state:duplicate Duplicate of already reported issue label Aug 19, 2015
@natanrolnik
Copy link
Contributor

@wouterds I suggest you to read the code of conduct before posting issues this way. Even though Parse may be a paid service for some users, their developers aren't supposed to deal with comments like this. Please be more considerate next time 😃 (I love this talk from @orta)

Not only it was a duplicate of another issue, as you posted, you could use CocoaPods to point to the previous version.

(If you don't know or don't use CocoaPods yet: it's a really good way to add 3rd party/open source frameworks, and I suggest you to use it. Will make it easier for you to update versions, and you won't need to download, drag and drop, etc. Take a look in this video that Google did explaining what is CocoaPods)

@wouterds wouterds changed the title Localization is fucked since Parse 1.8 Localization is broken since Parse 1.8 Aug 23, 2015
@wouterds
Copy link
Author

@natanrolnik: I was using Cocoapods and it didn't take any of the previous/older versions anymore, always picked 1.8 (in my Podfile I was using pod 'Parse', '~> 1.7').

Updated original post with more info and removed all the unnecessary rage.

@natanrolnik
Copy link
Contributor

@wouterds Hope it works for you now 👍🏻

@wouterds
Copy link
Author

@natanrolnik It does after removing derived data & updating to 1.8.1 👌!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:duplicate Duplicate of already reported issue
Projects
None yet
Development

No branches or pull requests

3 participants