I'm using plugin Xam.Plugins.Forms.KeyboardOverlap, but it seems that it doesn't work on my solution.
I added KeyboardOverlapRenderer.Init() in my appDelegate init.
I'm using 1.0.0.4 version of the NuGet.
I wouldn't recommend the package that Lucas Zhang has mentioned, since it hasn't been updated for 3 years now. Also, there doesn't seem to be any movement in the GitHub repo as well. You can see in their GitHub repository that it is pretty much left to be as is. There are some issues with iOS 13 and iPhone X+. Also, they have been planning to upgrade it for 2 years now, but to no success. See this in the issues.
If I would recommend a different package, it will be this one. It is the again a binding for IQKeyboardManager, but this time it is a fork of the repo and it is being maintained better than the original one. The current version is 6.5.5 and the last commit was 3 monts ago.
You can get the NuGet link here.
So, if you are going to choose a package, pick this one, as it has better support.
For Keyboard Plugin in iOS, I recommend Xamarin.IQKeyboardManager . Which is IQKeyboardManager binding for Unified Xamarin.iOS .
You just need to init it in your iOS project in forms and call the following code in AppDelegate.cs
Xamarin.IQKeyboardManager.SharedManager.EnableAutoToolbar = true;
Xamarin.IQKeyboardManager.SharedManager.ShouldResignOnTouchOutside = true;
Xamarin.IQKeyboardManager.SharedManager.ShouldToolbarUsesTextFieldTintColor = true;
Xamarin.IQKeyboardManager.SharedManager.KeyboardDistanceFromTextField = 300f;
For more details you could check Github Project Site .
Related
Can anyone suggest what to do about this message that I get when submitting my Xamarin Forms app to the iOS store?
Comment on possible duplicates
This question was asked before and not answered; I don't think an answered duplicate exists.
This is a known issue which was recently closed by the Xamarin team issue can be found here https://github.com/xamarin/Xamarin.Forms/issues/7323
And the fix is and i qoute
All the bits are in place, solution time! TL;DR: all is described in this piece of documentation here.
Make sure you are using the latest Visual Studio (for Mac) on the stable channel, that should put you on the right path. At the moment, you will need to use the Xamarin.Forms 4.5-pre1 preview release. I understand that this might not be an option for all of you, but rest assured, the stable package will be out well before the deadline. Stable 4.5 is planned mid to end of February.
Lastly, put the --optimize=experimental-xforms-product-type flag into your iOS additional mtouch arguments setting and you should get rid of the deprecation warning by Apple. If you don't have any references of your own to UIWebView of course 🙂
I would like to ask you to try this at your earliest convenience. Maybe not to release an actual new version to the store based on the Forms preview package, but at least upload a build to verify that this solution works correctly. Whenever you do, you can just update to the 4.5 stable package and release a new version with confidence.
If you do run into anything with this solution, please feel free to reach out to me directly (gerald.versluis [a with a long tail] microsoft.com) or open a new issue on the repository. Of course positive feedback is always appreciated as well 😉
I have some xamarin.forms 1.xx( I dont know which version) project on multiple platforms Android and iOS. And I've been asked to upgrade it to the maximum available right now version of xamarin.forms.
Therefore, I have 2 questions:
1) How to determine which version of forms I'm using right now (I'm working in Windows environment using Visual Studio 2015 ).
2) How to migrate/update to newest version of forms? (step by step, if it's possible). I have no idea how the result of that kind of operation supposed to look like, cuz I have never done anything like this before in my life. And what the best practices are?
What I've done is opened VS2015->Help->Xamarin release notes, however there was nothing about version of Forms I'm using. Also, I went to the official xamarin website and there was no guide how to do that. I also tried to look at the release notes the last Forms update and trying to find and fix differences, but my project is so big and I thought that this way doesn't seems right.
I'll answer first the What are the best practice regarding upgrading a Xamarin.Forms application? first and then address your other concerns.
I recently upgraded from 1.5.1 to 2.3.2, and from my experience, this is the steps to go through:
Decide which version you will upgrade from and to.
Read the change logs for all stabled releases between these two versions and look for breaking changes/bugfixes. You can find the release notes on Xamarin's website or on NuGet's website too.
Check regularly for new releases on the Xamarin.Forms forum and check if any reported issues may affect you. Every time Xamarin makes a release, there is a thread full of comments from other developers that may have encountered issues you might be interested in.
Using your favorite versioning software, make sure that all local changes are commited or stashed and create a new branch for your Xamarin.Forms upgrade (you don't know how long the upgrade will take and you still want to be able to send patches during the process)
Upgrade: Read the Important notes at Xamarin.Forms 2.3.2 release notes, especially the When upgrading Xamarin.Forms take care not to simply "update all" as ... part. Remember to upgrade on your PCL project, on your iOS project and on your Android project.
Test your whole app on as many devices as possible and for the longest possible period before you merge your branch back into your development/master/Main branch and address the potential incompatibility issues that may have been created in your development/master/Main simultaneously.
Step 3 is very important as it will allow you to reset back to your starting point and restart if you should fail to upgrade for whatever reason.
Xamarin.Forms is moving fast so it's important that you always keep an eye on what's going on even if you don't upgrade.
Which version am I using right now?
You can check that in the NuGet package interface or in the packages.json file in your project.
I am looking for clustering markers in MapKit, so I found this library: FBAnnotationClusteringSwift
that answers my needs.
But it is for swift 3.
Can anyone find the same library for swift 2.
Thanks.
I don't know if you found something else but here is your answer:
If you find something on github but it is in a newer version, you just have to search a previous version of this repo at the commits section.
This repo I think its working with swift 3 and swift 2 too (with pod install)
Maybe you faced a problem when you tried to insert his code from the usage.
Anyway this is the link for swift 2.2 if the pod installation is eventually for swift 3 use the manuall installation, just take the files and drop them to your project, and use the usage code to use the repo.
If you don't want swift 2.2 (so you have xcode < 7.3) I think this is this is the link
Hope it helps you.
I am new to xamarin and using XLab packages. I can see that Xlab packages are not stable yet however community is strongly supporting. In test
project I have added packages using Nugets. Now I found one issue in camera API of it so, how should I fix it. I have just
library files so, I can see code or fix it immediately.
Should I include the code of it? Because I can't wait for community to fix the issue and get the updated package of it? Yes If I will fix something then
I would love to contribute to open source community.
FYI: I am using PCL approach for development.
Best option would be to fork the GitHub repository and work on the sample application.
You can also get a copy of the source without cloning but then you cannot create a pull request for any code fixes. You can still report any bugs you find but it will be easier to contribute to the project by forking the project.
I wonder whether I should start development of a new iOS project in Xcode 4 or 3.2 - on one hand, I know 3.2 (a little), there is lots of info about it out there, and it's stable and proven. On the other hand, Xcode 4 brings some improvements as well. Are the newer previews of Xcode 4 ready for prime time, or are they still too buggy?
I'm especially interested in issues with (and recommendations of) externally hosted repositories, as I was not very happy with how Xcode 3.2 played with the Subversion repository in my last project.
Which one to choose, and which (preferably free and externally hosted) repository to match?
Today (3rd Feb 2011) Apple released the GM-Seed of xcode4. It's now ready for usage and you can compile your apps and release to the app-store. So if you are new with xcode, I would suggest using xcode4.
Why?
The new compiler has a lot of optimizations done. The compiler (as far as I can see the results) generates faster code. It's big fun!
The new Userinterface is more reliable. It makes your development a lot faster!
2a. Interface builder is now integrated. You can "drag and drop" your userinterface Item using the "ctrl"-key into your code and xcode creates the source for you! This accelerates creation of userinterfaces a lot!
git support has been added to sourcecontrol, which makes development in teams easier
The new LLVM compiler shows errors immediately while coding. And it displays errors, which xcode3 never mentioned
In xcode4 Apple changed a lot! So if you start with xcode3, you will have a new learning curve with xcode 4. For newbs I suggest: Download the xcode4 goldmaster and get startet with xcode4!
I second JackPearse's endorsement of Xcode 4, with one caveat. Been using Xcode 4 for a couple of days and am really starting to like it. Particularly like the way it shows the changes in each file as you commit. Unfortunately, when you delete a file, it forgets that it will need to be deleted in the repository as well. But the big BUT right now is that Xcode 4 will immediately crash the moment you try to do any Core Data modeling. See also XCode 4 Data Model Versioning bug? here on Stack Overflow. So, if you plan to use Core Data, you'll need to keep Xcode 3 around as well until they fix this.