I have followed advice from the following article:
https://devblogs.microsoft.com/xamarin/uiwebview-deprecation-xamarin-forms/
I am using the correct versions of:
- Xamarin Forms # 4.6.0.726
- Xamarin iOS # 13.16.0.13
I have set the flag in the mTouch arguments as --optimize=experimental-xforms-product-type --warn-on-type-ref=UIKit.UIWebView
I have set the Linker to 'Link Framework SDKs Only'
However I still receive the email from Apple stipulating the issue with UIWebView.
This leads me to believe that my code still has references to the UIWebView somewhere.
The warnings I get for this 4x - Warning MT1502: One or more reference(s) to type 'UIKit.UIWebView' already exists inside 'Xamarin.Forms.Platform.iOS, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null' before linking
But I don't know how to go ahead and find then remove these references.
Please can somebody offer some help?
Thanks in advance!
It seems as though --optimize=experimental-xforms-product-type does not strip out references to UIWebView from Xamarin.Forms.Platform.iOS. When using --optimize=force-rejected-types-removal it works. I've submitted to Apple and I did not get the email about UIWebView removal.
Related
The type 'ObfuscationAttribute' exists in both 'Leadtools, Version=21.0.0.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907' and 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
I'm just installed Leadtools.Camera.Xamarin NuGet in my existing application and getting the above error. In my existing App I'm using refit nuget as well. and this error came with RefitStubs.g.cs file .why this error occurring and how to resolve the above error in Xamarin.Forms. And the used version is 4.8.0.1821.
I tested by adding the Refit nuget package to our CameraDemo that’s shipped with LEADTOOLS 21 and building the project. This did not cause any compilation errors, even when adding code that uses the Refit classes in the C# code of the project.
This project is available with the full SDK installation under this folder:
LEADTOOLS21\Examples\Xamarin\CameraDemo
This means the problem is not likely related to using Refit and Leadtools.Camera.Xamarin together, but is trigged by something else in your project.
I recommend first to try to update your Visual Studio and its dependencies to the latest version.
If that doesn’t solve the problem, try to isolate the problem is a small test project that contains all the references from your main project but without the actual code (skeleton project, but with full references).
If this skeleton project triggers the same problem, send it to support#leadtools.com with details about the problem and our support staff will investigate it and get back to you.
I am trying to use Intents Extension in my existing Obj-C project for conversational shortcuts in iOS 13. I have followed all the steps and the procedures work fine in a sample app.
But when I try it out in my existing application the intents fail to launch and it is automatically redirected to my parent app.
The console error is as follows
[Intents] -[INCache cacheableObjectForIdentifier:] Unable to find cacheable object with identifier intents-remote-image-proxy:?proxyIdentifier=2A439A9B-6D95-BFB2-FCE4-31408D1E677F.png&storageServiceIdentifier=com.apple.Intents.INImageServiceConnection in cache.
Has anyone faced such an issue with intents? Please share your thoughts on this.
Additional Info:
The intent is registered. Have implemented the 'handle' 'resolve' methods and have also declared them in the interface.
Have the extension's min deployment target same as the parent (which created an issue that I had missed previously).
The issue was created due to setting up 'Copy only when installing' boolean as 'true' in 'Embed App Extensions' under 'Build Phases'. It was resolved once the check was made 'false'.
For the last couple of days it is impossible to access any documentation about APIs for Android SDK.
There is an error page with information:
"Unfortunately, the page you're looking for doesn't seem to exist."
Example link
The links have been cleaned up a bit, please update your bookmarks to: https://developer.here.com/documentation/android-premium/dev_guide/topics/maps.html
I saw some post about it but, unlike them, me it only happens since the update of VS2015 to VS2017, any idea?
at Xamarin.Forms.Platform.UWP.ImageRenderer.UpdateAspect()
at Xamarin.Forms.Platform.UWP.ImageRenderer.<OnElementChanged>d__3.MoveNext()
End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore()"
My project is a Forms Portable Project, tell me if you want any details, I'll edit the question ! Also, I use a renderer for Android, but not for UWP, it works on android, but it shouldn't be the problem since it worked before
Thank in advance
It's probably a bug in Xamarin Forms: https://bugzilla.xamarin.com/show_bug.cgi?id=37022
Updating Xamarin Forms should do the trick. I installed Xamarin.Forms version 2.3.5.239-pre3, which solved my problem.
see screenshot for the express version:
I have an Azure function (in Visual Studio), that triggers correctly an Service Bus event. In its run-method I want to call a method in a custom assembly. This works ok, until I use any method that uses Dynamics CRM assemblies. (I have tried both the assemblies from the downloadable sdk and the nuget package. I get the exact dll it asks for in the error message.
As soon as I call the my method I get the error below. I can run this exact method from a console app. (my custom assembly is a standard (not core) class library...
Additional information: Could not load file or assembly 'Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
This is not an answer, but rather an advice to anyone getting this problem (and its also a rant).
Avoid Azure functions at all cost and use "web jobs" instead when you can. After doing this with webjobs it was as simple as it should be, I have spent a week with different Azure-function-related problems
Cons with Azure functions:
Dynamic crappy scripting language (.csx), which gives you mysterious runtime error messages refering wrong places
Lock-in to azure platform
The usage on the browser editor is a joke unless its a really simple method and the error messages there comes up over and over again in least most annoying way (second to popups) and make you spread out your code
Pros:
Maybe you get a pad on the head from your MS-indoctinated architect for using the latest technologies so he might be able to squeeze in the word "Microservices" on some powerpoint presentation.