I am working on a Bluetooth application. I am using this Printer Framework. But I am facing "Lexical Preprocessor Issue". The file framework is present in the code still not working. I deleted the file and again added it but still no luck. Tried many things but unable to fix the issue. Please check the screenshot attached
Please help guys
Related
Hi I'm trying to run a Qt app on iOS Simulator. However, I am getting this error. Image is attached, please help me with this.
It was actually the problem with the Qt6 qmake. On macOS, I don't know why, but it generates the wrong path for the library files when I compile the app for iOS. I took help from this post and solved the issue.
I am currently developing an app using Xcode 11 and I am confused by the root of error message I am receiving when I try to build my app to run in the simulator. I have tried for hours to resolve this, using different tutorials I found on Stack Overflow but really haven't had any luck due to the fact most of the time these issues were reported for Xcode 11. The last time I had the software open, it ran totally fine so I'm very confused what changed since I last saved the project. If you can please help give some, that would be greatly appreciated. I have also attached an image of the error.
What I Have Already Tried
Cleaned the build folder
Manually cleaned the Derived Data folder
Raised the permissions of the executable within Finder
Check to make sure that the compiler is set to default in build options
Checked the info.plist and updated the executable file to ${EXECUTABLE_NAME}
Changed my derived data folder to another location
Deleted manually added folders
Restarted Xcode
Restarted my computer
Image of error as it appears on Xcode:
It appears that it's an iOS app, correct? With everything else you mentioned trying, there might be an issue with the simulator, so you could try running in a different simulator or resetting the current one to default settings. I've attached a screenshot and you can find this under the "Hardware" menu in the simulator. Note that it will delete all installed apps in the simulator.
I realized my issue was with a swift file that I made that was corrupted. The file was linked to a view controller and the view controller works fine but the class file was fully corrupted and would even make Xcode crash if I tried to open the file.
Tips for people who have the same issue:
Read through all the errors and find the specific file thats causing the issue. Usually the issue stems from dependency files but if you're lucky like me then its a simple fix
I uploaded a build to iTunes connect. When the processing gets completed, it shows the error,
'There was an error importing this build.'
I know this question has been asked before, but their solutions don't help me out. So I'm asking this question.
I have tried disabling bitcode. But it didn't work
For reference
Finally I got a solution.
Actually the issue was, I had GooglePlus library in my framework folder. I wasn't using it but it was there. Which not allowing the binary to be thinned. I just had to remove the GooglePlus library and it worked!!
My main app binary is not symbolicated correctly. But I see symbols from frameworks built with help of CocoaPods.
It is the same problem as described in this question:
Resolving problems in XCode 7 crash reporter
But answers for this question is not resolve an issue absolutely.
It's crazy to re-symbolicate reports every time manually.
And it's not really forward-looking idea to turn off bit code.
I fill the problem is somewhere in project configuration. Looks like CocoaPods do this the right way but I can't find suitable configuration for my app.
Do anybody know solution that solves problem fully once and forever?
Here the same project crash with bitcode turned off:
Now I am using Couchbase.Lite in iOS project, but it throws an error with Initialising in Linker Option with link sdks only,
Anybody has this kind of problem before?
But with don't link option, it works okay.
In this case, we can deduce the ipa size to publish app in App Store.
Can you help me out, if you faced this kind of problem before.
Thanks,
Please check this bug report: https://bugzilla.xamarin.com/show_bug.cgi?id=36255. Its been worked on.
The workaround for now will be to use "-nolinkaway" as this will only have a minimal increase in the final app size, unlike "dont link sdk".