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

Reference to FridaDeviceManager is ambiguous #5

Closed
klmitchell2 opened this issue Jun 27, 2020 · 5 comments · Fixed by #6
Closed

Reference to FridaDeviceManager is ambiguous #5

klmitchell2 opened this issue Jun 27, 2020 · 5 comments · Fixed by #6

Comments

@klmitchell2
Copy link
Contributor

Hey 👋 ,

I am trying to install frida-swift but I receive this error when I attempt to run the tests. Building the framework does not produce errors, but I am getting this compile error:
image

This is happening for FridaDevice, FridaSession, and FridaScript.

@oleavr
Copy link
Member

oleavr commented Jun 29, 2020

Hey!

This means the namespace we chose on the Swift side is unfortunuate, as it results in some of the Objective-C interop header types clashing with the C types. Either we will have to change our Swift namespace so this doesn't happen, or configure a different namespace for the Objective-C side only (if possible).

As a workaround you can probably disable generation of the Objective-C interop header.

@klmitchell2
Copy link
Contributor Author

What would be the best way to disable the generation of the Objective-C inter header? I'm unsure if this a flag at make core-macos-thin or when generating the dev kit?

@oleavr
Copy link
Member

oleavr commented Jun 29, 2020

It would be an Xcode project setting in frida-swift. I haven't investigated this but suspect it's in there somewhere.

@klmitchell2
Copy link
Contributor Author

Found the setting in Build Settings:

image

Changing from Yes to No fixed the issue.

@oleavr
Copy link
Member

oleavr commented Jun 30, 2020

Yay. Could you open a PR to change this? Don't think we're missing out on anything by omitting this.

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

Successfully merging a pull request may close this issue.

2 participants