I have followed the the instructions from Upgrading existing application manually
Its says :
If you are using the latest interim fix for IBM MobileFirst Platform
Foundation, link the IBMMobileFirstPlatformFoundation.framework and
"openssl.framework" files
My question is :
I cant find openssl.framework in Xcode 7.1. How to get this? (Does it obtain from this link?)
Why Worklight 7.1 need this?
Our Worklight version is : 7.1.0.00-20151107-1647
I am not sure those instructions are correct; see the instructions in the following tutorial: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-1/foundation/hello-world/configuring-a-native-ios-application-with-the-mfp-sdk/#addingNativeSDK
openssl.framework is not mentioned
I would change from manually setting it up to the new approach of using CocoaPods; going forward that is the only way to add the MFP framework.
It is inside the Framework folder. When i created the projects, the following files are added to Framework folder:
IBMMobileFirstPlatformFoundationHybrid.framework
IBMMobileFirstPlatformFoundationJSONStore.framework
openssl.framework
SQLCipher.framework
You might need to manually drag and drop those files.
Related
We are planning to upgrade our current implementation of identity server 3 to identity server 4. Is this easily achievable?
IdentityServer is compiled against both netstandard 1.4 and .NET 4.5.2 or above.
Our current project is in MVC and using .net framework 4.5.2. I have downloaded latest code of IS4 and added to my project. And there are separate library created for views/controllers.
For reference I am attaching screen shot of current code structure.
Do we have any step by step procedure available that need to be followed in this up-gradation process?
If I missed to share any information about project .. sorry in advance.
Please help!
They are completely different and there's no direct migration path unfortunately.
I am working on XCode 9.1 project that uses IBM Watson swift-sdk SpeechToTextV1 package. After upgrading swift-sdk to the version 0.19.0 and building XCode project the compiler error has occured: Missing required modules: 'SSCZLib', 'SSCommonCrypto' pointing to the import SpeechToTextV1 statement. swift-sdk updated via Carthage.
Cartfile content: github "watson-developer-cloud/swift-sdk".
command line update: carthage update --platform ios --no-use-binaries.
How can I include SSCZLib and SSCommonCrypto modules into XCode project?
Please help. Thanks a lot.
Use carthage update --platform iOS --no-use-binaries. It takes a while, but it works.
I'm afraid that I haven't been able to replicate the problem on my machine. I started with a new, empty Xcode project and was able to transcribe audio with the Speech to Text service.
I uploaded my app here. Can you try downloading it, adding your Speech to Text credentials, and running the app?
Please make sure that the newly compiled frameworks are the ones being used. Carthage does not place the frameworks in a custom location that is referenced in the project or workspace.
For me - in addition to building the library using --no-use-binaries flag - I also had to ensure that under my target's
Build Phases->Embed Frameworks
Build Phases->Link Binary with Libraries
SpeechToTextV1.framework is included
In addition - I found that these two files made all the difference inside the Carthage folder:
Carthage/Checkouts/ios-sdk/Source/SupportingFiles/Dependencies/Starscream/zlib/include.h
Carthage/Checkouts/ios-sdk/Source/SupportingFiles/Dependencies/Starscream/zlib/module.modulemap
I could only get this to work after my project was directly referencing the Carthage folder. Deleting either of these two files caused the error to return.
The v0.21.0 release of the Watson Swift SDK fixes this issue. You should no longer have to add a link to the zlib folder in your project settings. However, you will need to copy Starscream.framework into your application in the same way that other frameworks are copied.
The solution was to externalize the Starscream dependency. Adding Starscream as a recursive dependency for the Swift SDK allows it to build independently with its own environment. When the Starscream library is copied into your application, it should automatically include the SSCZLib and SSCommonCrypto dependencies.
We test each SDK before it's release, but this problem slipped past us. Our test machine happens to have other software that adds SSCZLib and SSCommonCrypto to the path, making it available to the Xcode build. It wasn't until we refreshed the machine with a new macOS install that we were able to replicate the problem. And with v0.21.0, that problem has been solved.
Sorry for your trouble and thank you for your patience while we tracked down the solution!
While Xcode was version 7.0 I had an app that worked perfectly well. I made the cocoapod file, set it up and everything ran perfect.
I just updated to 7.1 and now all I get are 21 errors that say "/Users/Johnathan/Desktop/Parse Default/GoogleMaps/Google Maps/Pods/GoogleMaps/Frameworks/GoogleMaps.framework/Headers/GoogleMaps.h:14:9: Include of non-modular header inside framework module 'GoogleMaps'"
I'm not sure what to do or how to update/edit this. I am not very familiar with cocoapods. Please help. I can't get my app to run. Thanks.
And if it helps all I did was update Xcode and it went from working to not working.
See this thread below for a solution as it seems to be most up to date.
In essence, you will need to add a Bridge Header (see comment 7)
Here it is: https://code.google.com/p/gmaps-api-issues/issues/detail?id=8524&can=1&q=Could%20not%20build%20Objective-C%20module&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal
I read the manual available here https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+SDK+Mavenizer. But it's confusing me. It's told that I should apply converter seprately to Flex SDK and Air SDK. But at present both of SDKs downloaded and merged by current Apache Flex Installer (should I download packages manually?). Also I don't have the flex-sdk-converter-1.0.jar. After build the mavenizer I have air-converter-1.0.0-SNAPSHOT.jar, flex-converter-1.0.0-SNAPSHOT.jar, base-converter-1.0.0-SNAPSHOT.jar and flash-converter-1.0.0-SNAPSHOT.jar.
How to use those tools to properly put Flex and Air SDK to the maven repositoy?
I also faced the same problem 2 months back.
The documentation on the website was for older version.
It has been updated on November 03rd.
Can you try again by following that?
This appears to be the current documented process now.
https://cwiki.apache.org/confluence/display/FLEX/Preparing+FDKs+for+Maven+builds
Alright what I noticed is that when I am developing against iOS 4.3, and I set my deployment target as iOS 4.1, I DO NOT get any kind of warning from the IDE about calls which are not supported in the minimum deployment target.
For example, calling [CLLocationManager authorizationStatus] shows no warning, despite the fact that the documentation for authorizationStatus says it was implemented in iOS 4.2.
I expect this would be a problem when wouldn't it?
From what I understand the solution to this is to download multiple SDK versions, temporarily build against the SDK for your minimum version, but switch to the current SDK version in order to ship.
If there is a better way to do this please advise. How can I get more options in Xcode under the "Base SDK" setting?
I expect this would be a problem when wouldn't it?
Yes, you'll generally crash if you call a method that doesn't exist.
From what I understand the solution to this is to download multiple
SDK versions, temporarily build against the SDK for your minimum
version, but switch to the current SDK version in order to ship.
That's a pretty good approach; probably the best way to find this kind of error semi-automatically.
If there is a better way to do this please advise. How can I get more
options in Xcode under the "Base SDK" setting?
You don't install all the SDK's together in a single "Developer" folder. Install each one separately -- there's an option to choose an alternate location when you install the SDK. Then it's just a matter of finding the copy of Xcode in the right folder and launching.
You don't need to have multiple options under Base SDK -- the normal practice is to just use the latest, but set the Deployment Target to the minimum version of iOS that your app supports.