I notice Google Play has flagged my AR apps developed in metaio with this message:
Security alert
Your app is using a version of OpenSSL containing a security vulnerability. Please see this Google Help Centre article for details, including the deadline for fixing the vulnerability.
Security alert
Your application has an unsafe implementation of the WebViewClient.onReceivedSslError handler. Please see the alerts page for more information."
I'm hoping it's an easy fix, such as replacing DLL files. Seems I have till July 11th to sort it.
Anyone had this problem and resolved?
Thanks
PS. I use metaio creator, output to arel, copy that output into an app folder template I created which I run through Android Studio/Xcode to generate the final build.
In case you are looking for alternatives, Wikitude came up with a fix a few days ago: http://www.wikitude.com/blog-sdk-update-openssl-upgrade/
Cheers!
Wikitude team
Related
Until three weeks ago, my application could upload it to the App Store without any problem. However, Apple has refused to upload the app with a new message about Non-public API usage.
The application is developed with Xamarin in Visual Studio for Mac and has updated all the libraries and packages. Can anybody help me? Because I can not find what the problem is, nor do I see any solution. It will be something new?
Thank you all.
Non-public API usage:
The app references non-public selectors in AppAytoSS.iOS:
addTemporaryAttribute:value:forCharacterRange:,
addTemporaryAttributes:forCharacterRange:, behaviorWithType:,
defaultBaselineOffsetForFont:, defaultLineHeightForFont:, finished,
greekingThreshold, horizontalCornerRadius,
initWithSource:convolutionState:weights:, initWithType:,
postSession:didAddPlayer:, postSession:didReceiveData:fromPlayer:,
postSession:didReceiveMessage:withData:fromPlayer:,
postSession:didRemovePlayer:,
postSession:player:didChangeConnectionState:,
postSession:player:didSaveData:, preferredMetalContext, removeData:,
removeTemporaryAttribute:forCharacterRange:, setGreekingThreshold:,
setHorizontalCornerRadius:, setIsPrimary:, setShouldAntiAlias:, setUUID:,
setVerticalCornerRadius:, shouldAntiAlias,
temporaryAttribute:atCharacterIndex:effectiveRange:,
temporaryAttribute:atCharacterIndex:longestEffectiveRange:inRange:,
temporaryAttributesAtCharacterIndex:effectiveRange:,
temporaryAttributesAtCharacterIndex:longestEffectiveRange:inRange:,
textContainerChangedTextView:, toolTip, usesBackgroundSession,
verticalCornerRadius
We had the (exactly) same problem with an Xamarin iOS Project and where able to fix it via Setting Build/iOS Build/Linker Behaviour: Link Framework SDKs only (before Don't link) - what Jack Hua link shows as solution.
We where not able, to figure out the problem behind though. Two different MacBooks where used, one with the most recent version of XCode, Visual Studio and Xamarin Libs, the other with slightly older versions. The latter was able to create an IPA without the above described error, the updated machine was not.
However the used NugGet Packages where the same, so I think this issue is not related to them.
After filling an internal issue with the Xamarin team, they advised doing the following
adding --linksdkonly to the Additional mtouch arguments on the iOS Build settings page
As it seems that Visual Studio ignores the settings in GUI
I have tested it and now get my build accepted by Apple without the above error
This is the issue filed on Xamarin
https://github.com/xamarin/xamarin-macios/issues/5913
I find a thread where people meet the same problem with you recently:build-status-has-changed-to-invalid-binary.
So, I guess some third part nuget packages you are using has updated and using these non-public selectors that Apple not allow.
I would suggest you to get you code three weeks ago and don't update any third part nuget packages. Then submit again to check if it is the problem.
You can also compare your reference with the references people listed in that thread and find something similar. And any nuget packages related to Player(As I can see some player selector in the non-public selectors list)?
Recently added Firebase Storage and Authentication to my Unity project. I work on Windows, have a single Unity Pro License, and want to export my App for iOS, as I have done many times before in this dev process.
However, since the addition of Firebase, I'm told I apparently can't export my Firebase-Enabled Unity project for iOS without swapping Unity to an OSX device (which I don't have in comparable quality).
I've noticed a singular thread here where a supposed workaround was discussed, but can't seem to pull it off myself:
"The plugin that comes with firebase depends on cocoapods to handle
transient dependencies. If you look at the Assets ->
PlayServicesResolver -> IOSResolver -> Settings
You can configure it to generate the podfile but not do the remaining
steps." - from user johnb003, March 18th 2017.
Can't seem to find the configuration settings described here. Scoured the forums/communities for solutions, but no results elsewhere.
So, that said, any other Firebase user have a workaround for this issue? I adore the collective Google has put together with their product, but I can't really afford to invest in another Unity Pro License just for the sake of working off of my sub-standard Macbook. Thoughts?
Looks like there's a Google Github project, Unity JAR resolver, describing how the Unity Play Services Resolver works for each target platform.
The documentation is pretty extensive, and solutions are use-case specific, so I can't give you much help on specific podfile settings, but hopefully you can sift through it yourself.
I am looking for documentation for Ace to do "Floating UI" , i want to to like facebook "Chat Heads". So far there is no documentation only mentioning coming soon , which means avaliable but undocumented right?. Is it already available in github latest master?
They decided to close the support for this project:
As of December 2016, this project is no longer maintained by Microsoft. We built ACE to provide developers with an “escape hatch” to access native code from within JavaScript. After nearly a year in production, we learned that most developers are satisfied with the access granted by Cordova’s Plugin Model. Thus, we’ve discontinued active development. We appreciate your interest in the project and hope you found it exemplary of Microsoft’s commitment to experimentation and open source software. if you're interested in continuing this project, please feel free to fork it. As of December 2016, we will no longer monitor or respond to open issues. You can keep up with other projects from Microsoft’s Cordova team by visiting http://taco.visualstudio.com. Thanks for your support!
I was also looking some plugin to implement "chat heads" in Cordova, without any luck :(
I am using Shinobi Grids 1.1 and I am looking to upgrade to 2.8. I cant seem to find any documentation on this online, does anyone know of any documentations online I can look to point me in the right direction? Please and thank you.
DISCLAIMER: I am a developer at ShinobiControls.
If you're a customer, you can download version 2.8.0 of ShinobiGrids from our customer portal. Otherwise, you can download a trial version available on our main site HERE.
Once downloaded remove the old framework from your project and drag and drop the new one in. You may get warnings and possibly some compile errors seen as you are updating from such an old version. However, any warnings you get should describe an alternative implementation.
If you get any compiling errors or warnings that aren't clear, just email us at info#shinobicontrols.com. A member of our team will get back to you as soon as they can.
I want to compile and use Xapian with xcode on iOS, is there any one with any experiments on this? Is it possible?
Is there any other option for implementing full text search on iOS?I have tried
S4luceneLib (in Obj-C) which works but is port of old version of lucene, also I
have checked Clucene and lucy, which like xapian i can not compile on iOS.
any help and comment will be appreciated.
Speaking as one of the Xapian authors, I don't recall hearing of anyone reporting trying to compile Xapian on iOS. I also don't know of any fundamental reason why it would be impossible to compile it on iOS. I suggest you contact the Xapian developer community (on the xapian-discuss mailing list: http://lists.xapian.org/mailman/listinfo/xapian-discuss or on the #xapian IRC channel on irc.freenode.net), and give details of the attempts you've made to compile Xapian, and the error messages or problems you encountered.