none
Installing vcremote on Mac gives error: framework not found MobileDevice RRS feed

  • Question

  • ld: framework not found MobileDevice
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    The framework is there.

    I see another person is experiencing same error here:

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/77545f82-6f66-47d6-b00c-02d73089cb00/installing-vcremote?forum=vcgeneral 

    by FreakyCoding (close to end of thread) and seems to be recent.

    Any help appreciated

    • Moved by Baron Bi Wednesday, October 25, 2017 8:37 AM Third party issue
    Thursday, October 19, 2017 1:02 PM

All replies

  • Hi John,

    thanks for posting here.

    >>ld: framework not found MobileDevice
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    As I said in another post, this forum is about c++ code issues with Microsoft products. For your case, please post on support team of VCRemote.

    Your understanding and cooperation will be grateful.

    Best Regards,
    Sera Yu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, October 20, 2017 1:40 AM
  • @Sera Yu, thanks for your hint! :)

    @John, I wrote the support team (support@npmjs.com). I hope they soon can help us somehow..

    Friday, October 20, 2017 6:52 AM
  • @FreakyCoding Thanks.

    I also emailed vcmdd-admin@microsoft.com with similar information.
    I do note that the issue seems to occur from installation of ios-deploy, if you install the latest version (1.9.2 vs 1.9.0 IIRC) using sudo, the error does not happen.

    Hopefully this can be resolved quickly.

    Friday, October 20, 2017 2:56 PM
  • Hey everyone. I've just pushed a new update to the npm vcremote package that should resolve this issue. Sorry about the delay in getting the fix out.

    Ian

    Monday, October 23, 2017 8:43 PM