MessagingRemoteException: An error occurred on client Build1660001055 while executing a reply for topic xvs/Build/16.6.0.1055/execute-task/CBREApp.iOS/e6f82e0002fCopy
TypeInitializationException: The type initializer for 'Microsoft.Build.Tasks.Copy' threw an exception.
PlatformNotSupportedException: Operation is not supported on this platform.
If you were like me who did not want to install the 16.7 Preview release just to get past this bug, the fix for this issue has luckily been released today (June 1st 2020) as part of update 16.6.1: Release Notes
Bug Report Link: xamarinios-fails-to-build-with-messagingremoteexce
(Note that as per this link, a temporary work around for this bug was to delete or change the build action of the iTunesArtwork#1x.png and iTunesArtwork#2x.png in your iOS project)
Related
In the latest beta 6 of Xcode 12, I'm having errors popping up when trying to resume a SwiftUI preview. The main error appears to be Cannot find type 'ASAuthorizationAppleIDButton' in scope. The code compiles perfectly fine when building or running on the simulator, and no errors show up. Only when I try to run a preview do things not work. Other errors I see are:
Type 'SignInAppleButton' does not conform to protocol 'UIViewRepresentable'
Cannot find type 'ASAuthorizationControllerDelegate' in scope
Cannot find 'ASAuthorizationAppleIDProvider' in scope
Cannot find type 'ASAuthorization' in scope
I have import AuthenticationServices at the top of my files. An important note is that the same project works perfectly fine without any errors on Xcode 12 beta 1.
A short term solution I've found is to remove all code using ASAuth (subsequently Signin with Apple) and switching from Firebase CocoaPods to their new Firebase Swift package manager. This makes previews work. Prior to switching from CocoaPods, I would get strange linker errors after removing ASAuth code.
My assumption is that I need to implement SwiftUI's new Signin with Apple button, but I don't know how to use it based on the little documentation provided by Apple.
This is the site my code references almost exactly the same: https://www.alfianlosari.com/posts/building-authentication-in-swiftui-using-firebase-auth-sdk-and-sign-in-with-apple/
I submitted an update to the app store today and received the warning Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs
I searched my app and found that I do not use a UiWebView.
Is the UiWebView used in Here SDK 3.12 or the MSDKUI 2.1.2?
Sources of NMAKit does not contain any reference to UIWebView. However, I found at least one internal third-party dependency, which contains such reference.
3.13.2 version is planned to be released next week. Will let you know, if quick fix has been found and included in 3.13.2 or in next HERE SDK releases.
UPDATE:
HERE SDK 3.13.3 includes fixes for UIWebView warning and is available now.
HEREMapsUI (MSDKUI) still depends on 3.12. Please wait for the next release. Integration is not public yet, once available it will be announced on the MSDKUI release page.
MSDKUI 2.1.2 does not have any reference to the UIWebView.
I found the UIWebView usage in NMAKIT
From terminal I changed directory to the latest Archive, e.g.
cd ~/Library/Developer/Xcode/Archives/<date>/myapp.xcarchive/Products/Applications/myapp.app
Then used nm:
nm GuideMeToHERE | grep UIWeb
for framework in Frameworks/*.framework; do
fname=$(basename $framework .framework)
echo $fname
nm $framework/$fname | grep UIWeb
done
The output I got was:
NMAKit
U _OBJC_CLASS_$_UIWebView
I was using FirebaseDynamicLinks in my Xamarin forms project (everything works fine) and I decided to update my nuget packages.. but after I update Xamarin.Firebase.DynamicLinks (and all dependencies) I got null after calling FirebaseDynamicLinks.Instance.
There was some major changes? Do I need to modify my code somehow after this update? Thanks for any help!
I found this in logs, so my google-services.json should be right, right?
FirebaseInitProvider: FirebaseApp initialization successful
Xamarin.Android SDK Version: 9.3.0.23
Operating System & Version: Win 10, 1803
So if not necessary now, suggest downgrading to previous version of Xamarin.Firebase.DynamicLinks. Maybe there are something not incompatible or new methods not be used correctly.
I have an old Asp.Net web application using Unity for dependency injection.
Today I updated the Unity using NuGet to the latest version. On trying to run the application, I am getting an exception:
Unity.Exceptions.ResolutionFailedException: 'Resolution of the dependency failed, type = 'SOME.Services.ISomeService', name = '(none)'.
Exception occurred while: while resolving.
Exception is: InvalidOperationException - The property converter on type DAL.Repositories.SomeRepository is not settable.
The exception happened on line
_someService = container.Resolve<ISomeService>();
I am very new to Unity. Could you please help?
The newer versions of Unity have breaking changes.
You may want to stick with the older versions of the DLL until you refactor the changes.
v4.0.1 Version 4.x is dead. Loss of original signing certificate made
it impossible to release anything compatible with v4.0.1 release. To
give original developers a credit only about 60 issues were found
during two years in production. To move on and enable further
development version v5 has been created.
v5.x Version 5.x is created as replacement for v4.0.1. Assemblies and
namespaces are renamed and refactored but otherwise it is compatible
with the original. v5.0.0 release fixes most of the issues found in
v4.0.1 and implements several optimizations but the accent was on
compatibility and if optimization would break API it was omitted. Once
stabilized, this version will enter LTS status and will be patched and
fixed for the next few years. There will be no significant development
in this line.
Check their road map here.
We are getting the following error on application launch.
MobileFirst Platform Foundation version 7.0
error response when calling : WL.Client.connect();
{"status":500,"errorCode":"UNEXPECTED_ERROR","errorMsg":"The server was unable to process the request from the application. Please try again later."}
error on server side
>com.worklight.core.auth.impl.AuthenticationFilter E FWLSE0048E: Unhandled exception caught: FPWSE0001E: Not Found - Targeted resource 'PushDevice' does not exist. Check the '17e57139-b8ff-3d29-b105-ddc44
2147adc' parameter
com.ibm.pushworks.server.exceptions.PushWorksEntityNotFoundException: FPWSE0001E: Not Found - Targeted resource 'PushDevice'
does not exist. Check the '17e57139-b8ff-3d29-b105-ddc442147adc' parameter
at com.ibm.pushworks.server.core.PushServiceImpl.updateDevice(PushServiceImpl.java:461)
at com.worklight.integration.notification.UserSubscriptionData.addSubscriptionDataToResponse(UserSubscriptionData.jav
a:87)
at com.worklight.core.auth.impl.LoginContext.addIdentityToJSONResponse(LoginContext.java:438)
at com.worklight.core.auth.impl.AuthenticationContext.addIdentitiesToResponse(AuthenticationContext.java:522)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:225)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:86)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:975)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1097)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:81)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:912)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:262)
at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:938)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
at java.lang.Thread.run(Thread.java:780)
But there is no issue while I am testing in my development machine.
The error message that you have provided matches the following APAR:
http://www-01.ibm.com/support/docview.wss?uid=swg1PI41837
As noted on the APAR page, this issue occurs when there are multiple versions of the application installed. The fix for this issue is included in build level IF201507012211 and above. I believe that if you check "About" from your MobileFirst console, you will find that the version that you have is earlier. My suggestion would be to apply the latest ifix to your Studio and Server environments, rebuild/redeploy your project war file, and verify that the issue no longer occurs. Ifixes can be downloaded from the IBM Fix Central site.
Please review the following link for information about installing the ifix and updating the server runtime:
https://www.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr_in_production_env.html?lang=en