I am creating an Iphone application wherein I need to process image and display it on application. I went through Aviary SDK which indeed really appeals to me as a developer. I went through its documentation which I understood very clearly.
The problem I am facing is in building the application. I receive a build failed when I try building application. I also went through GitHub repository CSPicker. Build also fails for that. I did every specific change mentioned in Prerequisites in the documentation. Still no success.
Following is the error I am getting:
Command /Xcode4.2/Platforms/iPhoneSimulator.platform/Developer/usr/bin/clang failed with exit code 1
I am using XCode 4.2 and iOS 5.0.
It's hard to say what is the problem. Likely you did not add necessary libraries to build with. Or used old compiler in settings (not LLVM)
As of right now Aviary has new version of SDK with decent description what needs to be done at http://www.aviary.com/ios-documentation
Related
I am new in Flutter Development and i have developed an app with Webview.
I have upload an apk on Google Play Store that is accepted but for App Store it shows some error.
Please find below error,
ITMS-90338: Non-public API usage - The app references non-public
symbols in Frameworks/Flutter.framework/Flutter: _ptrace. If method
names in your source code match the private Apple APIs listed above,
altering your method names will help prevent this app from being
flagged in future submissions. In addition, note that one or more of
the above APIs may be located in a static library that was included
with your app. If so, they must be removed.
For this error i have search many things but i am unable found any solution for this.
So please any one who is capable of solving this please help me to resolve this.
Thanks & Regards,
This happens if you are submitting the debug version to the AppStore, Flutter team recommends you to first run
flutter build ios --release
before archiving your app in Xcode.
First make sure you are submitting a release build with flutter build ios --release
If that's not the problem here you could find similar problems related:
flutter build ios --release may use a debug Flutter.framework by mistake
In my case, I updated my Mac to 10.15(Catalina), while the update my cocoapods installation wasn't there. So whenever I try to upload using the command flutter build ios --release and archiving it. Apple sent me the same email you received.
You can install cocoapods using the following commands.
step 1 Open terminal
step 2 command: sudo gem install cocoapods
step 3 set your project path on the terminal.
step 4 command: pod init
I hope it helps.
We tried to use speech recognition package - https://pub.dev/packages/speech_recognition in our flutter application along with other packages. The app was built successfully and installed, but we could see only a white screen on the iOS device. There was no error log that could tell us that this package created a problem. Once this module was removed we were able to see the application on the phone. This was done by manually checking for each package. I wanted to know if there is any runtime error handling methodology that could be used to log runtime errors and generate a logfile.
We are still researching on this issue, so we havent executed anything. Any suggestions would be welcome.
I am trying to publish the android app from SmartFace app studio and it is giving me an error to check logs. I am not sure where to find these logs. Publish to iOS works fine. Also I verified the android SDK is found in Project Details tab.
I have attached the screenshots here
This kind of publishing error can be caused by many factors. The ones that I know of are:
node.js that comes with Smartface is outdated, so you have to update it mannualy by going to its site and installing the latest version.
Sometimes Smartface says Java is found but it's not, so writing the correct directory could fix the issue.
I recently was trying to upgrade my react-native app to use react-native 0.5.0 and firebase. According to this article the react-native sockets are working and the full firebase sdk should be available.
I was previously using firebase-debug and #badfortrains react-native fork with success following the example project https://github.com/badfortrains/wsExample.
Since upgrading to I now am getting this error
When looking at the issues on the react-native repo I came across this https://github.com/sjmueller/firebase-react-native/issues/1
#stephenplusplus says he pushed a bunch of buttons and activated magic. Any idea what he is referencing??
There is also this other SO question Error creating user: { [Error: There are no login transports available for the requested method.] code: 'TRANSPORT_UNAVAILABLE' }
Any help on understanding the issue between using badfortrains with firebase-debug and the newest version of react-native with firebase would be appreciated.
I don't know if I am implementing something incorrectly or if the article mentioned above is a bit overzealous.
Thoughts???
Thanks.
Oddly enough starting a new project from scratch using the react-native-cli generator I was able to copy and paste all of my components over to the new project and have everything work perfectly.
I am not sure where the problem is but I will assume for now that there is an issue with the xcode project settings when trying to upgrade. Despite cleaning the project, resetting xcode to default settings, removing all derived data, restarting the package bundler, nothing worked until I created a new project.
This should prove there is nothing wrong with the JavaScript frameworks but rather it is some obscure xcode project setting. I will continue to look for a solution other than spinning a new project but for now it works.
When I build XDK for iOS, I get the message 'An error occurred while building the application. Verify your build assets are correct and try again':
I have searched online and checked the build assets, but can't find anything wrong, so I am stuck.
Is there any way that I can see the log for the build to tell what went wrong? I can't seem to find a link to the logs anywhere, either in the XDK application or the online AppCenter.
OK, I received a reply on the Intel forum to use the Cordova iOS build where there is a link to the build logs.
I was swapping between Cordova and legacy ad-hoc to try to get things working and maybe I got mixed up somewhere along the way. Anyway, I changed two things and it is building OK now with Cordova iOS: -
I found an android setting in the iOS config file that I removed.
I changed the app name, because I read that if it started with the project name that could cause issues.