AlamofireSwiftyJSON | Alamofire extension for serialize Data to SwiftyJSON | Build Tool library
kandi X-RAY | AlamofireSwiftyJSON Summary
kandi X-RAY | AlamofireSwiftyJSON Summary
Easy way to use both Alamofire and SwiftyJSON.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AlamofireSwiftyJSON
AlamofireSwiftyJSON Key Features
AlamofireSwiftyJSON Examples and Code Snippets
Community Discussions
Trending Discussions on AlamofireSwiftyJSON
QUESTION
I know this question has been asked a lot of times and there are many probable answer, but none of them helped me to get over my problem.
Here some possible solution's which I am trying out.
Solution1 Solution2 and many suggested solutions on the site.
I am also using Notification service & Notification Content Extension in my project.Also I am using firebase for push notifications.
From the time since I have integrated .xcconfig files to manage staging and production configuarations using This tutorial all the problems have started.
ANSWER
Answered 2019-Jun-11 at 14:01Follow these steps to find a solution.
From the logs I have posted above one thing is clear that the problem in my case was with Notification Content & Notification Service Extension targets
So following This Link based on -L or -R flag you are getting in the logs,
Delete the paths added for Library Search Path or Framework Search Paths as may be required.
For my case I had to do this for Notification Service & Notification Content Extension targets
This may cause more error where you might start getting errors for other framework or search path for same target (which was the case with me),
If such thing happen for any Target then try to delete the Other Linker Flags for the targets you are getting the error.
In my case deleting the Library Search Path & Framework Search Paths as well as Other Linker Flags Did the trick for me.
QUESTION
I'm using Xcode 9.0.
My pod file:
...ANSWER
Answered 2018-Sep-20 at 14:35Some libraries you use expect Xcode 10 (probably Firebase). Use Xcode 10.
QUESTION
When I try to upload the app to the app store using Xcode archive, following validation errors are coming up:
iTunes Store Operation Failed Invalid Bundle. The bundle at 'Dvp.app/Frameworks/AlamofireSwiftyJSON.framework' contains disallowed file 'Frameworks'.
iTunes Store Operation Failed Invalid Bundle. The bundle at 'Dvp.app/Frameworks/AlamofireSwiftyJSON.framework' contains disallowed nested bundles.
iTunes Store Operation Failed CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.swiftyjson.SwiftyJSON' under the iOS application 'Dvp.app'.
iTunes Store Operation Failed CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'org.alamofire.Alamofire' under the iOS application 'Dvp.app'.
I have referred these frameworks by drag and dropping them to the my project. I didn't use cocoapod or swift package manager to refer third party frameworks to the project.
Any idea how can I get rid of these validation issue?
Thank you
...ANSWER
Answered 2018-Mar-07 at 17:31After you archive the app , generate the ipa with AppStore selection , and upload it with Application Loader
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install AlamofireSwiftyJSON
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page