I'm trying to archive my app for submission, but I'm running into an error. In my app, I'm using the MBProgressHUD library, and the app works fine on the simulator, and all the devices I've tested on. However, when I go to Product > Archive, the build fails with the error saying:
MBProgressHUD/MBProgressHUD.h file not found."
Is there anything I had to do to prep the library? Any help would be appreciated, thanks!
~Carpetfizz
I just had to change the MBPogressHUD/MBProgressHUD.h to just "MBProgressHUD.h" in my files.
Related
I keep receiving this error when running my App.js for React Native that was working perfectly well before I attempted installing Victory charts. Somehow something broke and after over three hours of work I am unable to figure out a solution. I have tried everything I could find on the web including uninstalling watchman, reinstalling watchman, reverting to React Native 0.55.4, some other recommended commands. Nothing is working.I am so confused.
$ yarn add react-native-scripts
This helped.
I think the other library may hurt the installation part of your package. To solve this issue on IOS you need to add its library like below:
First do 'yarn add react-native-scripts'. In the case that it dose't work continue other steps.
1-Go to the node module of your project and find the package folder and find the ios file inside it.
2- Then drag it into ‘library’ section of your xcode. (It is the subset of your project folders)
3- Then go to ‘build phase’ and in the ‘Link binary with libraries’ add it there by clicking on the plus sign
4- Then in some cases you need to add the correct path of the ios file inside your node module in the xcode. To do that you should go to ‘build setting’ section in the xcode and search header there. Then you need to add the path there below other paths.
5- Then clear everything (cmd+shift+k) and then finally compile it.
I hope it works for you.
In my case the "crna-entry.js" file does exist in the roots and my project should work (nothing have been modified from last time when it does work).
After hours searching, finally I figured out the reason:
the packager's directory checking is case-sensitive and in windows terminal the drive "c:/" will not be auto-corrected to "C:/" which will lead to error.
Hope this will help someone who gets the same error.
Below is the full error message:
The development server returned response error code:404 Cannot find
entry file node_modules/react-native-scripts/build/bin/crna-entry.js
in any of the roots:
I am unable to add a new iOS app to fabric by following the instructions of the Fabric macOS plug in.
I have followed all of the instructions found at Crashlytics documentation
When running the app, I receive this error:
2018-03-12 14:22:24.090838-0400 [19139:8550117] [Crashlytics] Version 3.10.1 (129)
2018-03-12 14:22:24.636050-0400 [19139:8550293] [Fabric] unable to complete application configure: Error Domain=FABNetworkError Code=-5 "(null)" UserInfo={status_code=422, type=2, request_id=fbc432572e6f0e10f21d2ddc24c7f272, content_type=text/html; charset=utf-8}
I have tried searching StackOverflow and following answers, but no luck avoiding this error message.
Any ideas on this error message?
I had this problem and discovered that my 'visible' (in Xcode) info.plist was not a file in my root directory, and was an out of date version from earlier development activity. I am not sure why my correct/current info.plist did not display in Xcode. I found the current info.plist in Finder (it was in the root directory in Finder, just not appearing in Xcode). I dragged the file from Finder to Xcode and accepted all the defaults in the dialog that appeared. Then I simply built and ran the current scheme and all worked as it should.
Note: It appears that for some time I have been updating the 'invisible' info.plist directly from my apps Target / Info tab.
Make sure to include all dependency then throw a force crash or runtime error and do not forget to turn on your data or internet connection.
I'm running ....\bin\vsimporter.exe (with default settings) in my project folder and the .sln file seems to build successfully, but when I try running the simulator (on Win32 Solution Platforms, debug build), I get a bunch of errors. Most of the errors involve a missing file from the iOS 8.4 SDK (sys/types.h):
Error unknown argument: '-Xanalyzer'
Error 'sys/types.h' file not found
Error unknown type name 'XSym'
Am I supposed to include the iOS8.4 SDK? Any help/suggestions would be great.
I had the types.h problem too. Try to manually retarget to the Win 10 SDK:
Right-click on the solution and hit retarget, select the latest Win 10 SDK from the list, select all projects and click ok. The types.h problem should be gone.
Retarget answer worked for me to get rid of the errors with missing header files.
To get rid of the -Xanalyzer issue, I removed it from the .vcxproj file as a command line option using a text editor.
For the pods, I manually copied them from a Mac that already had them downloaded.
I'm getting this error after clicked for the first time in TEST-> Debug -> All Tests
I've been looking and seen something to add Pre build events but it didn't worked out, the error code:
Error 1 Could not copy the file "obj\Debug\qps-ploc\Bigbuilder.resources.dll" because it was not found. Bigbuilder
The program doesn't debug at the first try but when it asks "there was build errors. Would you like to run the last successfull build?" if i click no and retry to execute it will say nothing but the error will mantain in the error list
Uninstall the Multilingual App Toolkit from Programs and Features, download the latest version, and re-install. This fixes the build issues.
Encountered the same problem with building a console application using the Multilingual App Toolkit in a Portable Class Library, and now it is working.
This used to work for me, but now whenever I attempt to "Run in Simulator" with any of the iPhone or iPad types selected, I instantly get the console message
2013/10/1 10:4:48 Error: Script error. (URL: , LineNumber: 0)
I am working in the latest version of Chrome. Any help would be appreciated!
Just so that other users are aware, you can get that error on almost any problem in Mist and identifying the cause usually requires that we (I'm part of Icenium team) look into the specific project. In this particular case the problem was caused by missing App_Resources folder, which blaster has removed from his repository prior cloning it in Icenium. Generally an Icenium project should be able to function without this folder and we would fix this for the next version.