I am using version 6.24.3 of jxbrowser, and there is a problem when accessing https://mail.163.com. I can confirm that there is no problem with the website. I have checked the official jxbrowser documentation, but there is no gain. I hope to get an answer here
The following is the error message given by version 6.24.3 of jxbrowser；
This site can’t be reached
The webpage at https://mail.163.com/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SPDY_INADEQUATE_TRANSPORT_SECURIT。
I want to confirm what causes this, and if there is a solution on this version?
Exception screenshot
I suppose it's because of the old Chromium 69 used by JxBrowser 6.24.3. It's possible that the website doesn't work in such an old Chromium version. I can recommend that you try JxBrowser 7.11 based on Chromium 79 and see if it helps.
Related
I am experiencing an issue related to the displaying of any content within the JxBrowser, but only for 1 specific client PC.
The JxBrowser seems to correctly process the content that is sort of present, because if I click on an area where I know there is a link, the new page is opened (but not rendered too).
The "pages are not displayed" means that the content is completely white. Furthemore, the pointer is repetitively blinking between the normal arrow icon and the waiting circle, as something is going on in the background every about 1 sec.
A previous version of the application that embeds the JxBrowser doesn't produce the same problem.
Later on, I have also upgraded the JxBrowser version from the 6.23 to 6.24.3, but this did not solve.
Deleting any caches produced by the presence of the JxBrowser on the PC did not solve either.
What should I investigate to try and address this situation?
First of all, please note that JxBrowser 6 is no longer supported and it's a very old version based on Chromium 69. A lot of popular websites might not work properly in this Chromium version.
If the issue is reproducible only in a specific environment, then it's probably an environment-specific issue. If we are talking about rendering, then usually Chromium cannot render content when there's an issue with GPU drivers and the rendering mode (heavyweight or lightweight).
From our practice, disabling GPU very often helps in such cases. Please try passing the --disable-gpu switch and see if it helps. If it doesn't help, then the issue is probably in something else and additional research or even access to this environment is required. But again JxBrowser 6 is no longer supported.
As an option you can try JxBrowser 7 and see if it helps, but it's not that easy because this version has a new API which is not backward-compatible with the previous version.
I submitted a private windows app to Microsoft Store.
The app is c# framework 4.7.2 with Entity Framework, XAF and makes use of the Desktop Bridge.
When I try to install the app I get the above error code.
I have been able to install previous versions of the app.
I clicked the link "Get More Information About Faster Downloads." and turned off the attempt to use other nearby pcs.
I also encountered this issue for my own app on Microsoft Store suddenly. Turning off "Get More Information About Faster Downloads" doesn't help.
According to Ian Zheng from Microsoft, the code 0x80073CFB means that the provided package is already installed, and reinstallation of the package was blocked.
I just realised that my app was installed under another Windows account on the same PC. After I deleted it, the installation works again.
Hope this help anyone who has similar issue.
I have tried all the solutions which found on stack overflow, but still not able to resolve it. Somehow its not open the simulator and gives me error "unable to boot simulator".
I have reinstall 2 times xcode and also remove all simulator and add again. also change "DYLD_INSERT_LIBRARIES" to ZZ but no solution.
Please help me, Thanks in Advance!
Try to turn off System Integrity Protection http://www.imore.com/el-capitan-system-integrity-protection-helps-keep-malware-away - it helped me.
Problems:
As I also faced the same problem as below..
--"Unable to boot simulator"
--Storyboard designs/views completely invisible and showing only blue lines.
--CoreTelephony Trace File Error ... failed to create \tmp
Solutions
Don't do any SIP (Disable/Enable)settings its just temp solutions & it may harms to other applications in the mac as well as may affecting on secure data in the mac.
Best way to do upgrade your iMac to macOS "Sierra". It will solve all your problems.
Finally I am able to work on my project by solving above strange problems.
Happy coding.. happy Development...!!!
Assuming the error message was actually "Unable to boot the Simulator.", this error indicates an error starting up launchd_sim when booting the simulated device. In and of itself, it does not indicate the actual cause. You can look in ~/Library/Logs/CoreSimulator/CoreSimulator.log for more information about the error (including the error reason).
Possible causes:
On OSX 10.9 and earlier, DYLD_INSERT_LIBRARIES could be set by 3rd party applications. On later versions, invalid DYLD_INSERT_LIBRARIES are ignored instead of resulting in an error.
Usage of older simulator runtime DLC with Xcode 7 betas. Newer versions of Xcode ignore these older DLC.
If you need additional help, please provide that additional datum.
Also see my answer in the related question: Please see my answer on launchd_sim crashing: could not create temporary state directory regarding data you can collect to help further triage the problem.
I have searched around and have not found the particular answer that I am seeking for. I just went and updated my App to a Swift 3 Language from swift 2. It obviously threw out a host of errors which I went through and fixed to the best of my abilities and now I do not have any errors. I can run the app but I cant tell if anything else is working because the Login or Auth sections of the app are not working. I know that I can just bypass to test but I have been working on it a lot and trying to get this feature to work that worked well before the language was changed..
Very simple my question is this:
I upgraded to Swift 3. Do I need to upgrade the cocoa pods to support the change in language? If not is it just an issue with the way that my code is and because of the change to swift 3 that i need to keep tinkering with?
Thanks for any help
sorry posted that about 12 hours to early. After doing a lot of research it looks like I found the answer. have not tested yet but I think I am getting the same errors in the compiler.
"We've noticed what seems to be an issue with the latest iOS 10 simulators (up to beta 6 at the time of this writing) that causes Firebase Auth to throw an error due it to not being able to write values to the keychain. This issue does not affect real devices." This is from a Firebase Blog
Hello I got this problem on the device and not on simulator, my device is iOS 9.3.3 and the strange thing is that when run from xcode it works just fine
But when I open from device after stopping debug from xcode, the error will occur
And after some digging, I found out that if pod is only using firebase, it connect just fine even opening from the device
But if I add just 1 pod, it will error like above, so I don't really understand what is going on
And yes already try using keychain sharing
Any tips?
Edit: it works fine on other devices running iOS 8.1
I’m using the Windows 8 client and I can’t download an attachment.
When I try I get a message box saying “Downloading (NaN%)”
This works fine from an android device attached to the same server.
Any suggestions as to what the issue might be.
I needed to install the Microsoft.WinJS.2.0 (framework).
Once this was installed it worked fine.
I wasn't installing these using the IBMApplicationCenter so this wasn't pulled in automatically.
The Microsoft.WinJS.2.0 (framework) is available in the IBMApplicationCenter as a separate installable item too.