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

Missing required architecture i386 when build for profiling #993

Closed
Serproger opened this issue Apr 9, 2018 · 14 comments
Closed

Missing required architecture i386 when build for profiling #993

Serproger opened this issue Apr 9, 2018 · 14 comments

Comments

@Serproger
Copy link

Environment details

Info Value
iOS Version 11.3
Quickblox iOS SDK version 2.1.6
QuickbloxWebRTC SDK version 2.7
Xcode Version 9.3

Expected behavior

Application that uses quickblox webrtc can be built for profiling.

Actual behavior

When building I have this error:

ld: warning: ignoring file _/Pods/Quickblox-WebRTC/QuickbloxWebRTC.framework/QuickbloxWebRTC, missing required architecture i386 in file _/Pods/Quickblox-WebRTC/QuickbloxWebRTC.framework/QuickbloxWebRTC (3 slices)
Undefined symbols for architecture i386:
  "_OBJC_CLASS_$_QBRTCVideoFormat", referenced from:
      objc-class-ref in VideoController.o
  "_OBJC_CLASS_$_QBRTCClient", referenced from:
      objc-class-ref in VideoController.o
      objc-class-ref in AppDelegate.o
  "_OBJC_CLASS_$_QBRTCAudioSession", referenced from:
      objc-class-ref in VideoController.o
  "_OBJC_CLASS_$_QBRTCConfig", referenced from:
      objc-class-ref in AppDelegate.o
  "_OBJC_CLASS_$_QBRTCSession", referenced from:
      objc-class-ref in VideoController.o
  "_OBJC_CLASS_$_QBRTCCameraCapture", referenced from:
      objc-class-ref in VideoController.o
  "_OBJC_CLASS_$_QBRTCRemoteVideoView", referenced from:
      objc-class-ref in VideoController.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@ghost ghost added the duplicate label Apr 9, 2018
@ghost
Copy link

ghost commented Apr 9, 2018

#793

@ghost ghost closed this as completed Apr 9, 2018
@Serproger
Copy link
Author

It's not a duplicate. I've followed all the instructions in your issue, but nothing works. And this error can be observed ONLY when build for profiling (for simulator and for physical device).

@ghost ghost reopened this Apr 9, 2018
@ghost
Copy link

ghost commented Apr 9, 2018

@Serproger Could you please provide sample project with this issue?

@ghost
Copy link

ghost commented Apr 9, 2018

screenshot 2018-04-09 10 12 36

@ghost
Copy link

ghost commented Apr 9, 2018

@Serproger any updates?

@Serproger
Copy link
Author

For which project I should set this property? Pods?

@Serproger
Copy link
Author

Besides that, valid architectures for CocaPods project are i386, x86_x64. Is it valid to update them in the way mentioned in issue 783?

@ghost
Copy link

ghost commented Apr 9, 2018

For which project I should set this property? Pods?

For your project. For example : Targets - "<Your project name>" -" Build Settings"

@ghost
Copy link

ghost commented Apr 9, 2018

Is it valid to update them in the way mentioned in issue 783?

#783

?????

@Serproger
Copy link
Author

sorry, 793 :)

@ghost
Copy link

ghost commented Apr 9, 2018

Besides that, valid architectures for CocaPods project are i386, x86_x64. Is it valid to update them in the way mentioned in issue 793?

We don't support i386

Only:

//Simulators:
(for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64

//Devices:
(for architecture armv7):	Mach-O dynamically linked shared library arm_v7
(for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64

For Profiling, you should set "Build Active Architecture Only" to yes for "Debug & Release".

@ghost
Copy link

ghost commented Apr 9, 2018

@Serproger, any updates?

@Serproger
Copy link
Author

Yes, setting of "Build Active Architecture Only" works, thanks.

@ghost
Copy link

ghost commented Apr 9, 2018

@Serproger if you will have any other problems or questions please let us know by creating a separate issue.

Thanks!

@ghost ghost closed this as completed Apr 9, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
@Serproger and others