How to confirm correct changes of X509TrustManager Google Play warning issue? - android-security

I received warning message "Google Play warning: You are using an unsafe implementation of X509TrustManager". I removed problematic code and updated APK but warning still remains. It's probably because one of the libraries. Is there any change to confirm correct changes without releasing of APK?

Related

How to resolve warning related to deprecation

I am currently debugging my app for final submission. However, there are a lot of deprecation warnings poping up.
These aren't the files I wrote and I believe I implemented them through cocoapods. Some of them could be resolved, but when I try to click the fix button, Xcode tells me
...is locked for editing and you may not be able to save your changes. Do you want to unlock it?`
What should I do here? Should I click unlock and continue? What about the other warnings?
I implemented Firebase through cocoapods and set the deployment targets of all objects to iOS 14, which I believe is what causes all the warnings.

Connection to daemon was invalidated

My app is using Firebase Analytics and I believe starting in iOS 13.2 started getting the errors described here: Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?
I guess it wasn't a big deal
Since I planned for my app to go live in January, I began bigger tests in physical devices. I noticed after a while the app started to behave erratically, specially after receiving a [general] Connection to daemon was invalidated error. This doesn't occur in the simulator
Searching the internet I found a post that describes the same problem: https://forums.developer.apple.com/thread/124306
In my case, only Firebase seems to be calling WKWebView, but every time I open the UIMenuController I get the error described in the console and the app appears to be missing inputs. This is specially troublesome with UIScrollViews, which my app uses a lot. The pinch gesture seems to work at will. On an iPhone 6s, the issue isn't as noticeable, on an iPad, it's like a 50% chance the pinch gesture will work properly
Outside of removing Firebase, is there a way to mitigate this issue?
1 June 2020: The console message still persists, however, I have seemed to resolve the UIScrollView issue by deactivating delaysContentTouches, now the pinch gesture seems to work most of the time
23 October 2020 If anyone notices their app starting to behave erratically with no apparent reason I HIGHLY suggest to test it on an iOS 13 physical device if possible. Seems that Apple removed the warning from iOS 14, but testing it on iOS 13 you can pin point the exact reason after the warning appears in the console
Upon further testing, I've reduced the view down to a dead-simple UI view with a single SwiftUI TextField and the 'Connection to daemon was invalidated' still appears after I type the first character into the field. Soon thereafter the app crashes with a sigAbort. (So I don't think the reason is the UITextView wrapper I was using in the previous post). Once the invalidated message appears the app is doomed to crash, not right away but soon thereafter.
I have no idea what causes the 'invalidate' message and a Google search seems to imply that no-one else does either. Some folks appear to have made (experimental?) changes to their UI that stops the message but it appears to be impossible to determine a definite cause. (and like before it only occurs on a real phone)
Same issue without using Firebase at all. What I did: Delete build folder and compile again. Issue does not appears again.
On Xcode:
Clean the Build Folder
This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder.
On Flutter:
Just delete build folder.

How to remove this warning :

ERROR:browser_main_loop.cc(217)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
I have created the web browser using qt on ubuntu. Whenever I am running the browser I am getting the above-mentioned warning. I have to remove that warning. Can anyone please help me?

Does version need to be live to check if TrustManager error is fixed?

I'm experiencing the problem
Your app is using an unsafe implementation of the X509TrustManager
interface with an Apache HTTP client, resulting in a security
vulnerability. Please see this Google Help Center article for details,
including the deadline for fixing the vulnerability.
I needed to break my app's code to (i think) fix the problem. I need to know if the change is working, if so I'll fix the other problems the fix caused. If I upload the build to production using timed publishing but don't make the build live will it tell me if the error affects that build # in the popup error message?
Builds submitted using timed publishing will be flagged if they are affected.

How to solve? "An unexpected error occurred. Please try again."?

I go to organizer. I press
Devices
Then I go to editor and Refresh from developer portal.
I got this error:
An unexpected error occurred. Please try again. If the problem persists, please contact Apple Developer Program Support.
So I deleted all certificate or anything xcode related from my keychain. I deleted all certificate from apple developer center. Same problem.
Then I do it again.
First xcode says that there is no certificate. Want to make one. Sure.
Certificate is indeed created.
Then I got that message An unexpected error occurred. Please try again. If the problem persists, please contact Apple Developer Program Support.
It seems that I need to have some code signing identity. But how to make that and where is it? It's not available in itunes connect or apple developer program support.
I thought my certificate is my identity.
There is a similar question already. It says to delete both in Apple developer center and in xcode. I did that. It doesn't work.
Sometimes I got a message whether I want to sign with Looks like some key is wrong. But what?
When I tried to run a program I got:
(null): Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
When I go to organizer and submit my application to create that distribution certificate I got No identities available for signing.
So I download identities. Then I got an error occurred while attempting to download. Please try again.
There is also an option saying
Import developer profile. I guess I have to recreate this so called developer profile. What is it? And how?
According to this, after I create my first certificate I will be asked if I want to create a developer profile.
That never happens. I just got "An unexpected error occured" again.
Using xcode 5, I solved this by refreshing my provisioning profiles in preferences - accounts.
Hope this works for you.

Resources