-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
mediapipe ios build fails #50
Comments
It worked for me by changing "com.google.mediapipe.handtrackinggpu" with my identifier in BUILD file in /mediapipe/examples/ios/handtrackinggpu/BUILD |
this was the first thing i tried and it didn't work for me for python 3 / xcode 10.3 |
I've also created a provisioning profile with my identifier name and put it in the handtrackinggpu folder |
Yep I did this also and it didn’t work. :) but thank you for the suggestion! |
yearofthewhopper@, may I know your current issue? Is it still a cert-fail with DokRaphael @'s solution? |
Any combination of changing the preferences and trying to build the HandTracking example file fails. Using force python3 also fails. if I build from bazel bazel build -c opt --config=android_arm64 mediapipe/examples/android/src/java/com/google/mediapipe/apps/handtrackinggpu The behavior that happens is that the file will not open and if it does open then xcode crashes. There's no way to successfully build this example or any of the others. Is that enough detail? |
yearofthewhopper@, thanks for providing the information. Then, your problem is that xcode crashes when you run the .ipa in the simulator? I guess that's expected because the .ipa is for arm64, not for x86_64. Have you tried installing the app to a real device? |
I don't understand the expected workflow once you get the IPA. How can you get the app onto your phone if XCode crashes? seems kinda like a chicken and the egg situation here. So, yes I am trying to send it to my device but without it loading in Xcode I don't understand how that's possible. I am not trying to run it on simulator that would be pointless I don't know why you'd assume I was trying to do this? |
Once Bazel builds the IPA, you use Xcode to upload it to the device. In our instruction, there are two steps you need to do with Xcode after the IPA is successfully built by Bazel: |
yes this is the point. The IPA causes a crash of Xcode on load. I have read the instructions multiple times, though I appreciate you walking through the steps! |
@yearofthewhopper We are unable to replicate the crash on Xcode when loading IPA. It has worked for us on Xcode 10.2.1. Closed this issue for now until more info is provided |
…er_update_mediapipe_library Update hand landmarker library
Hi
the configuration file on each of the iOs examples points to a 9.3sdk / 10.0sdk simulator forcing a build-from-bazel to fail. The resulting errors in the configuration file being set wrong are multiple calls like this while bazel is building:
AVDepthData.h:75:12: note: 'AVDepthData' has been marked as being introduced in iOS 11.0 here, but the deployment target is _iOS 10.0.0_ @interface AVDepthData : NSObject
also while bazel is looking for the mobileprovisions file it has a cert-fail. The mobileprovisions also checks for a app identifier through bazel which also causes it to fail while looking for an app identifier namespace like "com.google.mediapipe.handtrackinggpu" instead of the user's *app identifier or allowing the user to set their own.
This makes your examples/ios completely un-workable.
#43 reflects this confusion as well
Please fix or update your documentation to reflect these errors.
The text was updated successfully, but these errors were encountered: