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

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.

Related

Shiny deployment - failed upload and gibberish in messages / error

The company I work for recently did something and I can no longer deploy my apps (including ones that work, have been previously deployed, and not changed since last deployment). The messages I get are... gibberish?
and
I couldn't find similar issues when googling. Can anyone shed any light? I don't even know where to start on fixing this... I'll be happy to add more info on session or whatever else as required.

Apigility admin screen is not showing my RPC Services

Not sure what I did and I can't seem to see my RPC Services anymore. They are there and I can see them and get responses to their paths, but I can't see them through the Apigility/Admin screen.
The error is telling that either the config files are missing or may be even the code itself. When the code is missing normally you see "Unable to fetch code" or similar, so most probably you are missing config files.
It could also be a simple markup problem due to a strange char.
Since the Apigility GUI uses the Apigility API, you can use Firebug to check what is wrong.
Open Firefox and check the tab "Network". Now try to create a service and check the requests, you will probably find a dump with the Exception / Error that you are looking for.

call timeout on apigee deploy flow

recently someone told me that the api was down and when I went to check I'm getting
<fault><faultstring>The Service is temporarily unavailable</faultstring><detail><errorcode>SERVICE_UNAVAILABLE</errorcode></detail></fault>
when I tried to redeploy Im getting the following error message.
http://cl.ly/image/1D2e0L1o2P0p
any clue on what to look for?
Marco
EDIT: the problem went away by itself. I dont like problems that disappear by themselves
There was an issue with some of the orgs in our cloud infrastructure, which should now be resolved. Please let us know, if you are still seeing issues.
You can find more details here: https://community.apigee.com/questions/8314/the-revision-is-deployed-and-traffic-can-flow-but.html

A custom proxy yields Incompatible magic value 1012089682

I have a custom http proxy that one worked. I have made some changes to its authentication process. And now when I try to launch an applet I get "Incompatible magic value 1012089682 in class file ...". Regular html files are transferred without any errors.
In my other web research I found this article http://arstechnica.com/civis/viewtopic.php?t=313827 discussing an ascii vs binary transfer issue.
My problem with debugging this is that the get of the jar file doesn't show up in tamper data on the browser nor in the access log of the webserver containing the proxy, nor in my proxy error log. So I am some what baffled. any help in how to get more information to solve this would be appreciated.
The technology is antique, but the company doesn't want to pay for upgrades. The proxy is an NSAPI plugin running in IWS 6 (SunOne webserver)
Thank you.
There was indeed a bug in my proxy code. I am not exactly sure what caused the symptoms described above, but fixing the code so that it didn't re-authenticate every time fixed my issue.

trying to find cause of Flex "RPC Error" pop-up

I'm working with a Flex 4 application (MXML and ActionScript front-end using BlazeDS and Java back-end) and I am trying to find the origin of an error.
The user sometimes (maybe once a week) gets a pop-up window with "RPC Error" in their web browser. If they retry the operation, they get the same error. Restarting the browser or maybe just reloading the page makes the error go away. Looking in the server log, I don't see any error on the server side. How can I figure out the cause of the RPC error? Can I configure some setting in the browser or Flash player to get additional info?
Thanks for any ideas. I've searched the web & some forums including SO but I've come up empty-handed.
Edit: in this case it appears the problem was loss of the network connection (user was connected via cell modem). I'm still interested in any ideas about how to troubleshoot this problem.
I like to do my development in Firefox and using Firebug as a console. When the Flex app starts, open up Firebug and look at the Net tab. It will bring up all the RPC calls made while Flex is initializing, which can be very useful for these kinds of bugs.

Resources