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
Related
though the docs here (https://learn.microsoft.com/en-us/graph/api/chat-hideforuser?view=graph-rest-1.0&tabs=http) said we could use them, with c# sample code too, but we don't see them at all after having added the sdk to the project. Note we are already able to add new chat with members and fetch messages.
a few others too that have same issue:
https://learn.microsoft.com/en-us/graph/api/chat-unhideforuser?view=graph-rest-1.0&tabs=http
https://learn.microsoft.com/en-us/graph/api/chat-markchatreadforuser?view=graph-rest-1.0&tabs=http
https://learn.microsoft.com/en-us/graph/api/chat-markchatunreadforuser?view=graph-rest-1.0&tabs=http
is there any dependency or steps we missed?
resolved the problem -- somehow the version (4.34.0) I used was out of date, and the latest version 4.49.0 does have these APIs
We identified one or more issues with a recent delivery for your app, "Steelpac Site" 26 (1.1.1.27). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.
Best regards,
The App Store Team
UIWebView is still in the iOS13 betas, so probably have until iOS14.
Apple UIWebView is only warning so this issue will be fixed after update code.
Please try:
1.Remove the Web View plugin:
cordova plugin rm cordova-plugin-ionic-webview
2.Add Web View plugin:
cordova plugin add cordova-plugin-ionic-webview#latest
3.Please check "Access-Control-Allow-Origin" https://ionicframework.com/docs/faq/cors#server-headers-response-
Hope your problem will be fixed.
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.
Naclsdk list indicates pepper_49 as the stable release
C:\nacl_sdk>naclsdk.bat list
Bundles:
I: installed
*: update available
I sdk_tools (stable)
vs_addin (dev)
pepper_44 (post_stable)
I pepper_45 (post_stable)
pepper_46 (post_stable)
pepper_47 (post_stable)
I pepper_49 (stable)
pepper_50 (beta)
pepper_canary (canary)
All installed bundles are up-to-date.
But: in API reference page
Pepper C API Reference (Stable) saying: lists the C API for Pepper 48.
Pepper C API Reference (Beta) saying: lists the C API for Pepper 49.
This makes me think pepper_48 instead of pepper_49 being the stable release.
Also note, pepper_48 is NOT listed in naclsdk list.
Can anyone help clarify this for me please?
Got a valid answer from Native-Client-Discuss Google Group as the following:
https://groups.google.com/forum/#!topic/native-client-discuss/6ormRPg8yE0
Sadly the NaCl SDK is behind on publishing new releases. We are
working working on fixing that now:
https://bugs.chromium.org/p/chromium/issues/detail?id=648344.
For now, please consider pepper_49 the latest stable release.
I am not sure why this question has been down-rated...
I create app with Realm database (RealmSwift)
When i try build app, there are a lot of errors , experimentally i found several libraries i should link to project for success compilation.
But i don't want to get it for final app version (size of app will very big), what to do ?
These frameworks for example:
CoreVideo.framework
CoreMedia.framework
AudioToolbox.framework
CommLibiOS.a
MediaLibiOS.a
My app doesn't use any video/audo/media features of Realm , i don't know why i need to link it.
If I try to delete for example AudioToolbox.framework from linked list , i have a lot of errors like this:
Undefined symbols for architecture x86_64:
"_AudioComponentFindNext", referenced from:
-[MPAudioUnitEngine voiceAudioUnit] in MediaLibiOS.a(MPAudioUnitEngine.o)
Why Realm needs these libraries?
p.s. sorry for my English
Realm doesn't require linking any of the libraries you've referenced. These must be referenced in your own Xcode project's configuration.
Realm Swift requires the following libraries to be linked: Realm, Foundation & libc++. Following the installation instructions in Realm's documentation should get all this set up properly: https://realm.io/docs/swift/latest/#installation
I suggest you look at some of the Realm example Xcode projects to compare and identify what you may be doing differently. https://github.com/realm/realm-cocoa/tree/master/examples