I am an android developer. I have a problem by using Fabric SDK for android.
I tried to integrate Twitter-Kit for my own implemented application.
My application android build version is Android 2.3.3 (Api level 10).
After adding kit-libs to my project i am getting compilation error because of some theme and resources are missed.
I figured out the root cause for the issues.
That is because of kit-libs android jars required android build version Android 5.0 (Api level 21).
So some of the resources are missed when i integrated the kit-libs to my own project which is supporting from android api level 10.
Please suggest me how can i use this Twitter-Kit( kit-libs) for my application which is build on android api level 10.
I am suspecting the issue with supporting libraries are mismatched in my application and integrated fabric twitter kit library apps.
Please let me know how can i check the problem with supporting lib's are not.
Please find the attached screen for my problem.
Finally i got answer for my question.
Root cause:
It is the problem when i integrate Fabric Twitter Kit into my application.
Some mismatch happen for my application targetSdkVersion and twitter library projects targetSdkVersion.
While integrating twitter the following property manifestmerger.enabled=true was added in my project.properties file. Because of this property my application is mismatching targetSdkVersion.
Solution:
Just commented manifestmerger.enabled=true in project.properties file.
Make sure is there any dependencies with that property before you are going to make comment out(or remove). For me it was added after integrating twitter kit for my android application.
Related
I maintain several iOS apps that use BlackBerry Dynamics Bindings for Xamarin.iOS. One of our apps has a production version that was build against version 6.0.1.6 of the bindings, along with an earlier version of the SDK and targeted iOS 12.
With iOS 14 coming out, it is time to rebuild the app, which means it is time to update the SDK, the bindings, and the dlls in my project. When I went to the developer portal, I found the SDK download page now has two options for the "BlackBerry Dynamics SDK for iOS". There is a "Static Framework v8.1.0.37" and a "Dynamic Framework beta v8.1.0.37".
According to the documentation, the dynamic framework, while in beta, does eliminate much of the complicated linking required in previous versions, and does away with the custom LD scripts for FIPS compliance. I would like to try it out, but I could not find an indication anywhere in the documentation files on the developer portal as to whether or not the Xamarin bindings work with this version of the SDK. Do they?
The currently available bindings are version 7.0, which target iOS 13; the iOS 14 readiness blog post says newer bindings are planned for mid-October of 2020. If the current bindings do not work with the dynamic framework sdk, is there any plan to have the next release do so?
The BlackBerry Dynamics SDK 8.1.x for Xamarin will not support using the dynamic library found within the BlackBerry Dynamics SDK for iOS. It currently only supports the static library. We do plan to add support for the dynamic library to our SDKs for Xamarin, Cordova and React Native in a future release.
I am trying to use "speech-to-text" functionality in xamarin ios. But I am getting following error after adding "Using Speech;" in my class file.
Your application is using the 'Speech' framework, which isn't included in the iOS SDK you're using to build your app (this framework was introduced in iOS 10.0.0, while you're building with the iOS 10.0 SDK.) This configuration is only supported with the legacy registrar (pass --registrar:legacy as an additional mtouch argument in your project's iOS Build option to select). Alternatively select a newer SDK in your app's iOS Build options.
How I can use "Speech" in xamarin ios app?
Check your Xcode version first. Whether is the latest version.
Check also iOS project Options->iOS Build->SDK Version, whether is using correct SDK version. For mine, it is set to Default which is 10.3 now.
After adding the Dropbox SDK Framework to my Xcode project (iOS) my project fails to build due to errors shown in image 1 below:
Prior to adding the Dropbox Framework, or reverting to the previous commit, results in the project building and running with out issue. I have also tested the same Dropbox SDK Framework package in a seperate demo project to ensure it is not corrupted - and that demo project builds and runs just fine, accessing the Dropbox SDK as expected.
Is it possible that the Dropbox SDK Framework is hiding or blocking access to the GLKit Framework within my main project?
Or is there something else at play here? The second error shown in screenshot claims the bridging header also 'Failed to import' which is an error I have not seen before, usually it is 'not found'.
The Dropbox SDK Framework is being added by drag-and-dropping into Xcode and checking the copy if needed box. Immediately after adding the Dropbox SDK Framework the project no longer builds and reports these errors.
I am answering my own question for anyone else who might have similar problems. While I did not find the root cause of the problem, I did get around it with the following solution.
I ended up removing all third party frameworks from my project which were:
ResearchKit Framework
Dropbox SDK Framework
Charts Framework
And in addition I removed all the XCode supplied frameworks from the project in the left hand file list: 'Project Title -> General -> Linked Frameworks and Libraries'
I then installed and setup CocoaPods with the project, and used CocoaPods to install and manage my third party frameworks (ResearchKit, Dropbox SDK and Charts)
The project is now able to build and run successfully and has access to the GLKit framework along with all other XCode supplied frameworks, bridging header and Dropbox SDK.
I assume this issue was due to a setting in XCode that was preventing access to GLKit after the Dropbox SDK had been added, and using CocoaPods to manage the integration of the third party frameworks skirted this issue.
If anyone has any further insight I'd be very interested to hear you explanation.
I'm trying to setup and install the ios connect sdk by following this tutorial. I'm using objective-c and my minimum deployment target is ios 9.0 . Ran pod install with the necessary pods and everything, but still getting several compilation errors including "Could not build module ADALiOS' and a bunch of errors in the ADPersistenTokenCache.h. I copied the source code from an existing sample project, so no exactly sure why the sample project works and my project doesn't. The only immediate difference that I know is that the minimum deployment target on the sample project is 8.0 while mine is 9.0 . Has anyone been able to install the ios connect sdk on versions of ios 9.0 and above, or have any idea what is going wrong?
Added image for reference:
NOTE regarding iOS 9
Apple has released iOS 9 which includes support for App Transport Security (ATS). ATS restricts apps from accessing the internet unless they meet several security requirements including TLS 1.2 and SHA-256.
While Microsoft's APIs support these standards some third party APIs and content delivery networks we use have yet to be upgraded. This means that any app that relies on Azure Active Directory or Microsoft Accounts will fail when compiled with iOS 9.
For now our recommendation is to disable ATS, which reverts to iOS 8 functionality
I've downloaded the latest AWS iOS SDK and added several frameworks (without copy) manually into my project.
Without further ado I got errors with a simple build:
Here's my architecture settings:
Since I understand none of the errors...
any advice would be appreciated.
You should follow the Set Up the SDK for iOS section of AWS Mobile SDK for iOS Developer Guide. You are not linking libsqlite3.dylib, libz.dylib, and SystemConfiguration.framework.
Try using this parameters:
Then, it is a good practice using cocoapods. AWS github has a great guide on how to implement their libraries (check the link):
Amazon Web Services SDK iOS Github