March 18, 2019 at 10:57 pm #1032745
I downloaded OpenEars last week. I can not build the project. audioPlayerBeginInterruption was deprecated as of iOS 8. Is there a version of the project that will build with current tools?March 19, 2019 at 7:23 am #1032748
Can you be most specific about what part of the project you can’t build and copy and paste which results you receive, which Xcode you’re using, and with which targets? A deprecation warning shouldn’t affect building.March 19, 2019 at 2:59 pm #1032750
Unfortunately, it is not a deprecation warning. It is an error. “Implementing deprecated method”
OEFliteController.m, lines 82 and 104.
I am using Xcode 10.1. I had been targeting iOS 11, but switching the build target to iOS 8 still produces the error.March 19, 2019 at 3:08 pm #1032751
Are you talking about the framework or one of the sample apps?March 19, 2019 at 3:30 pm #1032752
Hmm, looks like it is possible for Xcode to override the following build setting differently for different setups, unfortunately. I will fix this in a future version, but for now, please set the framework project’s build setting as follows:March 19, 2019 at 3:30 pm #1032753
OpenEars.xcodeproj produces the errors
I just tried OpenEarsSampleApp.xcodeproj. It builds and installs on my phone, but does not correctly recognize anything that I say.March 19, 2019 at 3:33 pm #1032754
OK, I’m not sure it’s constructive to troubleshoot the sample app’s recognition of your voice right now if you would like assistance building the framework. Have you given my suggestion above a try?March 19, 2019 at 3:35 pm #1032755
BTW, it shouldn’t be necessary for you to build the framework if you are just testing out the sample app for the first time – the cases under which a rebuild of the framework are needed/suggested aren’t that common.March 19, 2019 at 3:37 pm #1032756
Just to follow up, the sample app appears to (incorrectly) hear words when I use the phone’s microphone but when I try to use a bluetooth headset I get a message that the audio input is detected, but the input level does not vary from -120.March 19, 2019 at 3:39 pm #1032757
Are you finished with your question about building the framework?March 19, 2019 at 3:46 pm #1032758
New error: linker command failed with exit code 1
Edit: Sorry, should have been more clear. This error happens after making the changes to the build settings that you suggested above.
March 19, 2019 at 4:15 pm #1032760
- This reply was modified 4 months ago by Robert A Lynch.
Please set your project to the legacy build system.March 19, 2019 at 5:35 pm #1032761
Changed to legacy build system, still getting, still getting the same linker error.March 19, 2019 at 5:43 pm #1032762
I was able to replicate the issue, but it was fixed by that change. Can you describe to me how you changed the project to the legacy build system?March 19, 2019 at 10:40 pm #1032763
In Xcode: File/Project Settings…
Changed both Shared Project Settings and Per-User Project Settings to Legacy Build System
then Product/Clean and Build
“Linker command failed with exit code 1”March 19, 2019 at 10:45 pm #1032764
OK, in that case I’m afraid I can’t give you more assistance with this at this time since I can’t replicate that this issue persists with the build system changed, and the error shared doesn’t have information about the specific build error in the logs.
However, I have made a new release today which doesn’t demonstrate this issue based on my earlier replication of your issue, so you’re welcome to download it and see if it helps you: https://www.politepix.com/wp-content/uploads/OpenEarsDistribution.tar.bz2
- You must be logged in to reply to this topic.