I have a created a fresh QML quick application using Qt 5.3.2 on Mac. When I build it has 2 link errors.
Failed to parse qmlimportscanner output.:-1: error:
[iphonesimulator-debug] Error 66
I have not even made any changes to default application, why do I get these errors and how can I fix it?
I know this question is pretty old, however, as I just encountered the same error and finally managed to solve it: Your Project Path must not contain spaces for qml quick projects on ios.
Please do not ask me how or why this is the case (as it clearly works for desktop or android deployment), but this was the issue for me. After moving the project to a different location (a folder that does not contain spaces) it would run qmake and deploy just fine.
Related
This has been killing me for the last couple of days. I have read everything I can find on this error and have done what xamarin says but it still doesn't work.
I can't get my builds to get through azure pipeline xamarin.ios build and deploy to apple.
When I build locally I get messages like
MTOUCH : warning MT1502: One or more reference(s) to type 'UIKit.UIWebView' already exists inside 'Xamarin.Forms.Platform.iOS, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null' before linking
with a companion message that says no references after linking
when I use --warn-on-type-ref=UIKit.UIWebView with the optimize arg.
When I build on azure in my pipeline, I only see the MT1502 but nothing saying anything after linking. The build gets submitted to Apple and fails because of the ITMS message.
I don't know what to do. I am using the latest macOS vm image, mono 6.8.0.123, xamarin.ios 13.16.0.13, xcode 11.4.1. The pipeline worked fine before April 30 deadline, now no matter what, I can't get the linker to strip UIWebView.
Let me know what other info would be helpful. I am completely stuck at this point.
Thanks.
I just got my build to pass Apple's inspection.
What ended up working for me was building locally and packaging the ipa file. On my mac I then changed the ipa extension to zip and unzipped it. I used terminal to go to the YOURAPPNAME.app "folder" and used grep -r UIWebView . to search for references. Don't forget the . so it searches the current directory. I missed that at first and got some message that grep was listening on stdin.
For me that resulted in a line like this:
Binary file ./Frameworks/PersonalizedAdConsent.framework/PersonalizedAdConsent matches
Now, the important thing to note is the linker never warned about this, so I was completely unaware of it. In my case it was part of Firebase/Admob. I was only one release behind and updating to the latest fixed my problem.
I still am using --optimize=force-rejected-types-removal --warn-on-type-ref=UIKit.UIWebView -warnaserror:1503 as my mtouch args. But builds now get through.
I hope this helps point you guys in the right direction, I've spent the last 3 days just trying to get builds to upload reading every post I could find on the web on this problem.
Solved !! I had to update the way how nugets are included to the iOS project .csproj file. The problem was that linker despite the --optimize=force-rejected-types-removal flag was not removing the UIWebView component form Xamarin.Forms 4.6 probably because it did not see it.
My project was created over two years ago and I was still using the packages.config file. After the update the flag started to work and grep query returned 0 :). The best way is to compare the old .csproj file with freshly created iOS project .csproj file and see how VS is referencing nugets.
When I first run this option in first picture, I get the error in second picture.
However, if I create a new project with current project's files, this option is working well. I don't know why this happens. Can anyone help me solve this? Thank you so much.
I have search much solutions, but neither did them work for my situation.
The application exited with an error (ExitCode 1)
Qt creating new translation (ts) using Visual gives error - (ExitCode 1)
How to make QtLinguist shipped with Qt 5.9.1 work?
I have fix this problem. Our project list contains one item that its related local file is deleted by others, and I just remove this item. Now everything just be fine. The .tf file is now can produced by Qt tool.
I asked this on the Xamarin forums but got no response.
Running my app in debug mode works fine, but when I try to run in release mode, I get these errors:
Error Payload contains two or more files with the same destination path 'e_sqlite3.dll'. Source files:
C:\Users\Bob.nuget\packages\sqlitepclraw.lib.e_sqlite3.v140\1.1.8\runtimes\win10-arm\native\e_sqlite3.dll
C:\Users\Bob.nuget\packages\sqlitepclraw.lib.e_sqlite3.v140\1.1.8\runtimes\win10-x86\native\e_sqlite3.dll
I have seen other posts where some users have updated the nuget for UWP and others that have actually deleted one of the dll's, but none of these work for me; when I try to delete one of them, I then get an error that it is missing, so not sure what to do.
I have deleted my nuget folder and re-got everything fresh, cleaned my solution, rebooted, but nothing seems to work.
Well, I ended up opening an issue with Microsoft over it and turns out that I had the build target set to ARM (Project properties->Build->Platform Target) which apparently tries to copy 2 different versions. I set it to x86 and works fine.
The issue for me was that the project was set to target x64 in the project properties, but when I debug, I debugged using x86. The moment I switched to debug using x64, it worked for me.
I'm trying to add ParseKit to a new command line project in Xcode, but the framework shows as red in the Project Navigator. When I try to build, I get this error
error: /Users/acdlite/Xcode/Chemistry Parser/../parsekit-trunk/build/Debug/ParseKit.framework: No such file or directory
I've followed the directions given by the developer in this answer: How to embed ParseKit as a private framework in a Mac App bundle.
To my knowledge, red indicates that the file is not at the specified location. The file inspector says it should be located at /parsekit-trunk/build/Debug/ParseKit.framework, which actually doesn't exist if I try to navigate there in the Finder. So then where is it located? I have no idea.
I've followed all the steps from scratch like a dozen times now, including checking out the code via SVN. It's driving me crazy, and I feel like an idiot. I wish I could be more specific but I am truly lost as to where to go from here.
Alright, after at least 20 attempts I eventually got it working. Mostly, I followed the steps given by the developer in this answer: How to embed ParseKit as a private framework in a Mac App bundle
However, following the steps exactly didn't work. For the life of me, I couldn't get the ParseKit framework to show up as an option when I attempted to add it as a dependency of my Target. Xcode would just say "No filter results found." So I skipped that step. I also did not add a "Copy Files" build phase. Doing so resulted in a dependency error.
This was way harder than it should have been, and I don't know if that's because I'm stupid or Xcode is poorly designed. Probably a combination of both.
By the way, I'm using Xcode version 4.6.1 (4H512).
I am having a trouble to get IntelliJ IDEA 9.0.2 to run FlexUnit4 tests. The tests won't be performed because of the following error:
Error: Unable to resolve resource bundle "<some name>"
So I checked the build.xml whether the path-elements are set properly:
<path-element>resources/locale/{locale}</path-element>
This is working for the normal build process perfectly fine. Therefore, I am pretty confused and would appreciate any ideas that help to get the tests to run.
The Flex libraries have resource bundles that sometimes need to be included. I added
<Flex_SDK_location>/sdks/4.1.0/frameworks/locale/en_US
to the build path and it fixed an "Unable to resolve resource bundle" error for me.
I had this same problem. I saw the suggestion in the other answer to add a path with the locale in it, and though my framework was set up correctly (and I couldn't manually edit any build path in the IntelliJ configuration), it did lead me to the problem.
Go to the "Flex" Facet in the module and click onto the Advanced tab. The problem is if the Non-default locale settings is checked and blank, then it doesn't assemble the correct path and find your framework.
To fix it, simply uncheck the "Non-default locale settings":