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

Setting deployment target to 8.0 causes demo app to crash #126

Open
jamesalvarez opened this issue Sep 1, 2016 · 2 comments
Open

Setting deployment target to 8.0 causes demo app to crash #126

jamesalvarez opened this issue Sep 1, 2016 · 2 comments

Comments

@jamesalvarez
Copy link

I notice the demo has it's deployment target set to 5.1, but I would need to use the library in a minimum 8.0 environment, so I've checked with the demo and aside from the 'AudioSessionGetProperty is deprecated' errors etc, I get an 'Assigning retained object to unsafe property; object will be released after assignment' in AudioFileReader.mm line 221 - and this seems to be the line which causes the demo app to crash. I got around it by setting line 50 to: strong rather than assign - but have not thought about whether this is just a hacky workaround, since when running it again with a 5.1 environment, it doesn't let me do that....

@alexbw
Copy link
Owner

alexbw commented Sep 1, 2016

If it works, it works. I haven't done any work on this project on a few
years, so whatever you can do to patch it up is appreciated! Please do open
a PR if the solution you found works.
On Thu, Sep 1, 2016 at 9:03 AM jamesalvarez notifications@github.com
wrote:

I notice the demo has it's deployment target set to 5.1, but I would need
to use the library in a minimum 8.0 environment, so I've checked with the
demo and aside from the 'AudioSessionGetProperty is deprecated' errors etc,
I get an 'Assigning retained object to unsafe property; object will be
released after assignment' in AudioFileReader.mm line 221 - and this seems
to be the line which causes the demo app to crash. I got around it by
setting line 50 to: strong rather than assign - but have not thought about
whether this is just a hacky workaround, since when running it again with a
5.1 environment, it doesn't let me do that....


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#126, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ4jxM341U1DpQIY3dDSBebwcQzE9cyks5qls00gaJpZM4JyqjD
.

@jamesalvarez
Copy link
Author

It works - but then prevents it working when having the target as 5.1... I will leave it for the time being.

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

2 participants