Last week I could navigate to edge://flags/#allow-insecure-localhost and I could edit the flag so that my localhost could serve invalid SSL certificates. Today after the latest Edge update (Version 88.0.705.50) I can no longer find this flag.
Has it moved to another secret area? How can I allow insecure localhost SSL certs again for my application?
This seems to be an issue with Edge 88.0.705.50. In higher version, Edge 89.0.767.0, the flag comes back again:
I think the issue will be fixed in future version of Edge Stable. You can wait for the updates and download Edge Dev to test your app as a workaround for now.
Related
When accessing Crashlytics via the "Beta" webclip I can sometimes see the list of builds, but when I cannot, or if I do see them, and tap on a build, I see a message at the bottom of the screen stating
Server Error
Something went wrong. Please try again.
[OK]
I did check the Profile for crashlytics, and found the signing certificate for *.crashlytics.com had expired on April 7th 2017.
I removed the profile, rebooted my device, and reinstalled the profile via accessing the check me out option in one of the builds. I checked the expiry date for *.crashlytics.com and it was newer (April 6th 2020)
For the first attempt afterwards, I was able to install a build, but occasionally on subsequent attempts I saw the aforementioned server error, or the screen indicating the device is not set up for beta testing.
Can someone explain exactly what is happening and how to properly resolve this, as it is impacting the ability to complete work due to being unable to install builds reliably. Having to remove and reinstall the profile - which works for a while - isn't an acceptable method to resolve things.
You're missing a final step.
You need to install the Certificate manually, it would be waiting for you to install it once you get into the Settings native App.
1. After this, go to Home > Settings (no need to close the Safari web)
2. Then install the certificate on Settings / Check top.
3. Go back to the browser and install the App.
If you are having trouble with this error on iPad, check that you are viewing the mobile website (tap the AA button in the search bar and then Request Mobile Website).
Each subsequent page load may revert back to desktop, so check that setting each time it fails.
Xcode 7 is not authenticating the GIT/TFS Credential.
It was working in the previous version of Xcode 7.
It seems to be an issue with Xcode7, many others also met this situation.
Try to use below workaround:
Switch on basic authentication in IIS on your TFS box.
or
Go to Xcode->Preferences and under the accounts remove all the repos
you may have there.
Close all your projects and then kill Xcode. Make sure to wait a
couple of seconds (we speculate this is needed to let Xcode kill
everything as one colleague here had to do it twice).
Then restart Xcode and re-open your projects so that it re-adds all
the repos using the corrects credentials.
More detail info , please refer this link XCode 7, git broken
I'm referring the apple's documentation herehttps://developer.apple.com/library/mac/documentation/IDEs/Conceptual/xcode_guide-continuous_integration/PublishYourCodetoaSourceRepository/PublishYourCodetoaSourceRepository.html#//apple_ref/doc/uid/TP40013292-CH8-SW1.
The 'Connect to Remote Repositories' options is not been displayed.
As far as I can see, previous versions of OS X Server required you to add remote repositories, whereas v3.2.1 just uses the ones set up in Xcode itself. In what seems to be the most up-to-date version of the Continuous Integration Guide, the "To add a remote repository to the Xcode service" section has been removed completely, and the "Configure the Xcode service to connect to your remote repositories" line has been moved above the instructions for adding repositories to Xcode, all of which seem to support that.
Having said that, I currently can't get mine to work so I'm waiting on Apple Support to get back to me, but I think that's the theory!
Since my upgrade to WL 6.2 direct update isn't working anymore on iOS.
What I'm trying to achieve is to get direct update working with the iPad and my windows machine. This way I can develop on my windows machine and use direct update to push my changes to the iPad (iOS 7.1.2). Following scenario describes my problem.
Create a new WL project in worklight studio on Mac (just installed the latest WL plugin today (platformVersion=6.2.0.00.20140724-2139). Add iOS as environment and replace the main.js with the following code:
function wlCommonInit(){
WL.Client.connect({
onSuccess: onConnectSuccess,
onFailure: onConnectFailure
});
}
function onConnectSuccess() {
WL.Logger.debug("Connect success.");
}
function onConnectFailure() {
WL.Logger.debug("Connect failed.");
}
Run the project as an Xcode project and use Xcode to deploy the application to an iPad. Now follow the following steps to reproduce the issue:
Make a modification in the index.html
Redeploy the app on your local worklight server in eclipse
Kill your app and restart it again
The direct update is working and your changes are reflected in your app. Yeah!
Now as a very basic next step, try to use the direct update with a Custom Server URL. Thick the Use custom URL checkbox in your iPad settings and change the Custom server URL to the URL of your local server.
When I now retry step 1 to 3, the direct update fails. On startup the app informs me an update is available, and when I click update the downloading progress bar appears but stays at 0% forever. In the custom server URL I only changed the IP to the IP of my macbook and removed the dash after the project name. I also tried changing the URL to the URL of my windows development machine (also with the latest WL eclipse plugin), but this results in the same behaviour.
One last remark; I would expect that when I disable the Use custom URL checkbox; direct update would work again. But this is not the case.
I've tried this and I cannot confirm it not working.
Added your code snippet to main.js
Enabled worklightSettings in application-descriptor.xml
Run on Worklight Development Server
Open project in Xcode
Run
Make a change and re-deploy
Verify Direct Update is received
Quit app
Make a change and re-deploy
Open myapp settings via Settings.app and enable Custom Server URL. The URL is already pointing to my (same) server
Open app
Verify Direct Update is received
You mentioned in the comments that once enabling the Custom Server URL option you also need to change the server address to another - I suggest to double-check you are indeed inputting the correct address. Maybe you have several network cards or alike.
Reinstalling eclipse resolved the problem. After reinstalling eclipse I also get the correct IP for the custom server URL in the server connectivity settings.
I updated my BB10 DEV Alpha device for a firmware update on 10.2.For that I download the Dev Alpha B 10.2 from this url https://developer.blackberry.com/blackberry10devalpha/devalpha_update.html after which updated the device with the downloader as per the instructions given after the firmware updated my device didnt boot and became dead can anyone help me in this issue .
I have a BB10 DEV ALPHA A device.
Dev Alpha B update doesn't work for Dev Alpha as per I know. I have also tried to upgrade, but as it didn't worked I downgraded it to previous version.
Also, this is mentioned on BB Website.
Note: You may attempt to load the latest Dev Alpha B update onto your Dev Alpha A, however the The Dev Alpha A is no longer officially supported as of 10.1.0.1485. If you encounter any issues please downgrade back to 10.0.10.263 using the Autoloader method. You can download the old 10.0.10.263 Autoloader here.
https://developer.blackberry.com/blackberry10devalphas/update/