Android Support V4 Jar Download
- Android.support.v4.app.fragmentactivity Jar Download
- Android Support V7 Jar
- Java Jar Download
- Android Support Library V4
About the Android Support Libraries
Google has created support libraries to make new features available to older versions of Android. In general, Support Libraries are given a version number in their name, which is the lowest Android API Level they are compatible with (eg: Support-v4 can only be used on API Level 4 and higher. More info in this Stack Overflow discussion).
Two of the support libraries: Support-v4 and Support-v13 can not be used together in the same app, that is, they are mutually exclusive. This is because Support-v13 actually contains all of the types and implementation of Support-v4. If you try and reference both in the same project you will encounter duplicate type errors.
Problems with Referencing
Since Support-v4 has become so popular, a lot of 3rd party libraries now depend on it. They could have chosen to depend on Support-v13 instead, but it's more common to depend on v4 since that gives any apps using these 3rd party libraries the option of supporting API levels all the way down to 4.
Download android-support-v4.jar from Mafia-download.com. This file android-support-v4.jar is hosted at free file sharing service 4shared. If you are the copyright owner for this file, please Report Abuse to 4shared. The android-support-v4.ja r is in library folder, but B4A 5.8 now is looking a different file???. Com.android.support:support-v4.jar now I cannot work with B4A 5.8 neither with B4A 6.0, I think the easy is put to work B4A 5.80 I am 100% stuck.
问题根源：因为在复制项目的jar包时，把Eclipse下自带的android-support-v4.jar包复制到了‘android-support-v7-appcompat’ Library项目下，替换掉了原本的android-support-v4.jar，而Eclipse自带的版本较低，导致报错。 Recommend：eclipse - The import android.support.v7.app cannot be resolved.
If a Xamarin 3rd party library references the Xamarin.Android.Support.v4.dll binding to Support-v4, any app that uses this library must also reference Xamarin.Android.Support.v4.dll. This becomes a problem when the same app also wants to use some of the functionality from the Xamarin.Android.Support.v13.dll binding to Support-v13. If you reference both bindings, you will encounter duplicate type errors.
Type-Forwarded v4 Binding Assembly
To get around this problem, we have created a special Xamarin.Android.Support.v4.dll assembly which has no implementation, but simply [assembly: TypeForwardedTo (..)] attributes which forward all of the Support-v4 types to the implementation within the Xamarin.Android.Support.v13.dll assembly.
This means a developer can reference this type-forwarded assembly in their app which will satisfy the reference to Xamarin.Android.Support.v4.dll by any 3rd party libraries, while still allowing Xamarin.Android.Support.v13.dll to be used in the app.
NuGet Assistance
While a developer could manually add the correct references necessary, we are able to use NuGet to help choose the right assembly (either the normal v4 binding or the type-forwarded v4 assembly) when the NuGet package is installed.
So, the Xamarin.Android.Support.v4 NuGet package now contains the following logic:
If your app is targeting API Level 13 (Gingerbread 3.2) or higher:
Xamarin.Android.Support.v13NuGet will automatically be added as a dependency- The type-forwarded
Xamarin.Android.Support.v4.dllwill be referenced in the project
If your app is targeting anything lower than API Level 13, you will get the normal Xamarin.Android.Support.v4.dll binding referenced in your project.
Do I have to use Support-v13?
If your app is targeting API Level 13 or higher and you choose to use the Xamarin Android Support-v4 NuGet package, then the Xamarin Android Support v13 NuGet package is a required dependency.
We feel the very minor increase in app size (the two .jar files differ by 17kb) is well worth the compatibility and fewer headaches it results in.
If you are adamant about using Support-v4 in an app that targets API Level 13 or higher, you can always manually download the .nupkg, extract it, and reference the assembly.
Android.support.v4.app.fragmentactivity Jar Download
Example steps for Xamarin.Android.Support.v4
Download the desired Xamarin.Android.Support NuGet package (forexample by installing it with the NuGet package manager).
Use ildasm to check which version of android_m2repository.zipthe NuGet package needs:
Example output:
Download android_m2repository.zip from Google using the URLreturned from ildasm. Alternately, you can check which version ofthe Android Support Repository you currently have installed in theAndroid SDK Manager:
If the version matches the one you need for the NuGet package, thenyou don't have to download anything new. You can instead re-zip theexisting m2repository directory that is located underextrasandroid in the SDK Path (as shown the top of theAndroid SDK Manager window).
Calculate the MD5 hash of the URL returned from ildasm. Format theresulting string to use all uppercase letters and no spaces. Forexample, adjust the $url variable as needed and then run thefollowing 2 lines (based onthe original C# code from Xamarin.Android)in PowerShell:
Example output:
Copy android_m2repository.zip into the%LOCALAPPDATA%Xamarinzips folder. Rename the file touse the MD5 hash from the previous MD5 hash calculating step. For example:
%LOCALAPPDATA%XamarinzipsF16A3455987DBAE5783F058F19F7FCDF.zip
Android Support V7 Jar
(Optional) Unzip the file into %LOCALAPPDATA%XamarinXamarin.Android.Support.v423.4.0.0content(creating a contentm2repository subdirectory). If you skipthis step, then the first build that uses the library will take alittle longer because it will need to complete this step.The version number for the subdirectory (23.4.0.0 in thisexample) is not quite the same as the NuGet package version. Youcan use ildasm to find the correct version number:
Example output:
Download the desired Xamarin.Android.Support NuGet package (forexample by installing it with the NuGet package manager).
Double-click the Xamarin.Android.Support.v4 assembly under theReferences section of the Android project in Visual Studio forMac to open the assembly in the Assembly Browser. Ensure that theLanguage drop-down is set to C# and select the top-levelXamarin.Android.Support.v4 assembly from the Assembly Browsernavigation tree. Locate the SourceUrl property under one of theIncludeAndroidResourcesFrom or JavaLibraryReference attributes:
Download android_m2repository.zip from Google using theSourceUrl returned from ildasm. Alternately, you can check whichversion of the Android Support Repository you currently haveinstalled in the Android SDK Manager:
If the version matches the one you need for the NuGet package, thenyou don't have to download anything new. You can instead re-zip theexisting m2repository directory that is located underextras/android in the SDK Path (as shown the top of theAndroid SDK Manager window).
Calculate the MD5 hash of the URL returned from ildasm. Format theresulting string to use all uppercase letters and no spaces. Forexample, adjust the URL string as needed and then run the followingcommand in a Terminal.app command prompt:
Another option is to use the csharp interpreter to runthe same C# code that Xamarin.Android itself uses.To do that, adjust the url variable as needed and then run thefollowing command in a Terminal.app command prompt:
Example output:
Copy android_m2repository.zip to the$HOME/.local/share/Xamarin/zips/ folder. Rename the file to use theMD5 hash from the previous MD5 hash calculating step. For example:
$HOME/.local/share/Xamarin/zips/F16A3455987DBAE5783F058F19F7FCDF.zip
(Optional) Unzip the file into:
$HOME/.local/share/Xamarin/Xamarin.Android.Support.v4/23.4.0.0/content/
(creating a content/m2repository subdirectory). If you skipthis step, then the first build that uses the library will take alittle longer because it will need to complete this step.
The version number for the subdirectory (23.4.0.0 in this example)is not quite the same as the NuGet package version. As in theildasm step earlier, you can use the Assembly Browser in VisualStudio for Mac to find the correct version number. Look for theVersion property under one of the IncludeAndroidResourcesFrom orJavaLibraryReference attributes:
Additional references
- Bug 43245 –Inaccurate 'Download failed. Please download {0} and put it to the{1} directory.' and 'Please install package: '{0}' available in SDKinstaller' error messages related to Xamarin.Android.Support packages
Next Steps
Java Jar Download
This document discusses the current behavior as of August 2016. Thetechnique described in this document is not part of the stable testingsuite for Xamarin, so it could break in the future.
Android Support Library V4
For further assistance, to contact us, or if this issue remains evenafter utilizing the above information, please seeWhat support options are available forXamarin? forinformation on contact options, suggestions, as well as how to file anew bug if needed.