In Flash Builder 4.7 i get the following error message
The Flash Builder debugger failed to connect to the running application.
Ensure that:
For in-browser applications, you are running the debugger version of Flash Player.
For network debugging on a mobile device, you have a reliable network
connection to the device, and port 7935 is open on your machine's firewall.
I have tried
Reinstalling Flash Builder
Starting a new project
Reinstalling Java
Restoring system point
Reinstalling Firefox and flash debugger version for it. verified at this site https://helpx.adobe.com/flash-player.html
All of the steps listed "https://forums.adobe.com/thread/672635" in every post
every related post on stack overflow
Plus some others.
Please if anyone has any more ideas, I'm completely lost as to what to do, If I can't get somewhere on this by this afternoon then I'm probably going to just commit to spending a few days reformatting my drive and reinstalling everything.
Related
I am trying to build a Xamarin iOS app and debug it in my mac simulator from Windows. I haven't been able to get this working all day and it is pretty time sensitive at this point.
I have updated and ensured both VS mac and windows are on the same update channels, have the same versions of Xamarin installed, cleared the cache on both mac and windows, made sure I can SSH into my machine, I can actually run the mac agent on a remote machine over VPN, but the connection is EXTREMELY slow and it is causing all sorts of different issues so debugging with it isn't an option.
The only thing I've noticed is that everyone else who seems to have this issue and shares info from their Xamarin diagnostic output shows that they're installing from Broker 4.6.* while mine seems to be trying to install Broker 1.1.6.*. This seems pretty odd, but I don't really know anything about this as I have nearly zero background in Xamarin and have just picked up this project as my company's Xamarin dev left last summer and I am developing a NativeScript app for us... someone thought they were kind of similar I guess?
Anyway, here is my output from when I attempt to connect... lastly, I used my mac's IP because the windows parallels install couldn't resolve the machine name and pointing localhost or 127.0.0.1 doesn't seem to work either although I'm not entirely sure why.
Checking host configuration for connecting to '192.168.86.29'...
Checking SSH configuration...
Checking available disk space...
Checking Mono installation...
The required Mono version to install on the Mac couldn't be determined, so the Mono validation will not continue.
Checking Xamarin iOS installation...
The required Xamarin.iOS version to install on the Mac couldn't be determined, so the Xamarin.iOS validation will not continue.
Checking host configuration for connecting to '192.168.86.29'...
Host '192.168.86.29' is configured correctly
Starting connection to '192.168.86.29'...
Installing Broker 1.1.6.181...
Unable to install the Broker
Starting connection to '192.168.86.29'...
Starting disconnection from 192.168.86.29...
Starting disconnection from 192.168.86.29...
The connection to '192.168.86.29' has been finished
An error occurred while trying to start the Broker...
I have spent the better part of a day trying to connect to PAServer on MAC OSX from my Windows PC with no luck. I am not sure what I am missing.
I am using Delphi 10.2 Tokyo on Windows. Trying to connect to PAServer 19.0 on a Mac Mini running macOS Sierra (10.12.4) on which I already have XCode (v8.3.2) installed along with Command Line Tools.
Both the dev machine as well as the Mac Mini are connected to the same Wifi network. I even tried connecting both machines to a different network but with the same issue.
I get the same error message every time that the connection failed. I suspect that it has something to do with the network - where the 2 machines cannot see each other, but I don't know how I can confirm this or resolve it. I have tried to search on SO as well as online but have not found anything that has helped.
Has anyone seen this issue and overcome it? Is there a set of steps I can go thru to troubleshoot this? Any help or guidance would be most appreciated!
OK - I kept trying out different things and was able to solve this issue (one way to solve it I guess).
Because it seemed like it was network related, I tried first to create a hotspot with my phone and connected the dev machine and the Mac Mini to it. The PAServer connection worked.
So I looked for a way to do this via Windows. Here are the steps I followed:
Open Settings > Network & Internet (on Windows 10)
Go into Mobile Hotspot and select Wi-Fi in the Share my
Connection From dropdown
Set a Network name and Network password
Turn on Share my Internet connection with other devices
Now on the Mac, connect to the network name we set up in step 3 and enter the password that was set. Then start PAServer on the Mac. That's it!
Now when you connect from Delphi to PAServer, the connection succeeds.
Note: Interestingly, when I was not using the mobile hotspot method on Windows, the IP address on PAServer (and on Windows) was 10.xx.xx.xx. With the mobile hotspot, the IP address is 192.xx.xx.xx.
I just configured (today) a new macos sierra with paserver. yes it's painfull :(
don't use virtualbox (it's buggy and slow), but use instead VMware, it's work like a charm. it's much more easy to have only one computer to develop than 2. also you can copy/past the log or anythink else from macosx to windows (or vice-versa) in just one click. and you will not have any internet problem or anything else ...
Part 1 - Description of the problem
I have the DK2 and I am working on a VR project. This project uses FirefoxNightly. I've downloaded it and installed the WebVR Enabler Add-On
Got this from http://mozvr.com/downloads/
I have also downloaded and installed the latest SDK and Runtime for Windows from https://developer.oculus.com/downloads/
I am also getting this on the Oculus Configuration Utility (while the oculus is plugged in):
However, I have gone on another computer with windows.. installed everything just like on this windows computer and it clearly shows the Oculus Rift connected properly but the head tracking still not working.
EDIT: I just tried connecting the oculus rift to this "second" pc ( dell laptop ) and now it doesn't even recognize the oculus rift. Still no head tracking.
EDIT 2: I tried installing everything on a third PC without success. I'm getting "service unavailable" on the Oculus Configuration Utility
My display mode is set as shown in the image.
Part 2 - Questions
What am I doing wrong? Is there a step I forgot to do? The weird thing is, I have the same project running on Mac without having any problems. Yes, on windows I can see the screen through the oculus rift but head detection is just not present.
Part 3 - list of possible fixes that did not work
This reddit post talks about the firewall issue however I tried the oculus rift with the firewall disactivated without success.
This reddit post talks about a possible fix by reinstalling everything and updating certain drivers.. however I have followed this fix step by step without success.
This oculus forum post talks about the issue and one person proposes a fix that worked for him/her. I followed the fix without success.
Part 4 - System info
If you require specific translations let me know. It is in French.
Part 5 - List of things I have tried that have been thought of
I have reinstalled everything. SDK (is not even needed in fact), runtime, firefoxnightly, webvr add-on multiple times
I have rebooted my computer multiple times
I have tried the different Rift Display Mode
Basic demos from mozvr.com and other webvr based projects work fine but head tracking does not work.
My Oculus is not broken (maybe for windows), it works fine for the Mac.
I've tried using different HDMI cables and Different minUSB-USB cables without success.
Part 6 - Quotes from the forum
First post
This sounds like the same issue a lot of us are having with the 0.5
and 0.6 versions. It's not something wrong with the cables, but with
the Runtime itself. Direct-mode works flawlessly and in Extended mode
the rift still displays a picture, altho without any tracking etc from
the runtime. Hoping it'll be fixed in the next update.
I've seen head tracking break in Firefox Nightly sometimes but I can usually solve it by restarting the browser once or twice, assuming that the hardware and Oculus side of things is working correctly.
Today, most games made for the Oculus Rift are based on specific versions of the Oculus Rift. I found this GUI desktop application that seems to solve most of those problems.
The idea is to install all Oculus Rift Runtime versions and then use the GUI to switch between each version.
The link above is to a reddit post that talks about how to install the application and the different runtimes.
You must install the runtimes from oldest to newest otherwise you'll run into some difficulties, like I unfortunately did. If I'm not mistaken runtime version 0.8 is very buggy and I never really got it to work.
Good luck.
This is what I did to get the Oculus DK2 working on my Windows 10 Laptop:
Create a windows restore point before you start this.
Download oculus_runtime_rev_1_sdk_0.4.4_win.exe from the Oculus downloads page.
Run the installer. Do not restart your computer when prompted.
Go to C:\Program Files (x86)\Oculus\Service folder, right click on OVRServer_x86.exe and go to properties.
In the compatibility tab, check Windows 8 mode, and Run As Administrator.
Run OVRServer_x86.exe
That's it.
The Good News
You should now be able to run direct to rift games. The HELIX rollercoaster app works well. So does the 6000 Moons demo. Most others do not. Depending on the game, you may need to go to your windows display settings, and fiddle with the screen resolution and rotation of the Oculus display.
The Bad News
Your computer may not restart. When I did the above, and later restarted, the computer hung on the windows loading page. I had to go into advanced start mode and load a system restore point. Definitely not the best user experience, but at least I got something working.
I have been developing a Windows phone app on my lunch breaks at work and spare time at home. The project is stored in my Dropbox so it's the same on both pcs. At work when I debug/deploy to the device everything is fine and dandy. At home however I get the following.
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Now in both cases I'm using the same version of the SDK and of VS on the same Microsoft account on the same phone on the same project. But it doesn't work.
I have reinstall the SDK twice now to no avail.
When I run the device registration I get the following message.
Unable to connect to a phone. Make sure the Windows Phone IP over USB transport service is running
I'm not sure what I'm doing wrong here, has anyone run into this before? Any ideas of a fix for the issue?
Update:
I have uninstalled 2013 r4 and installed 2015. I have done a hard reset on my phone. I have run Windows Update and I'm up to date. I have tried making brand new projects as some of the posts suggest, to no avail. Same issue occurs, except now my emulators get:
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '184901A8-DC44-4CED-869E-DC7733D048D6'
I'm guessing the next step is reinstalling Windows, I think I'll just wait till Windows 10 comes out.
Possible Fixes:
1.Try reconnecting your phone.
2. try re registering your phone as developer device
3. try this fix
https://dev.windowsphone.com/en-US/OEM/docs/Phone_Testing/Configuring_IP_over_USB
Testing apps on windows phones can be frustrating. One common problem I get is the need to reinstall drivers for the phone. I think this may be your problem.
The other problem similar to this I've encountered, was when registering for windows phone not using the correct version on that pc for 8.0 or 8.1.
Aside from this, there is a list with links provided that may help you. Let us know how you get on.
This link Problems and fixes when registering a Windows Phone 8 device to deploy/debug applications covers the major issues, some mentioned by Akash.
The following is a summary of the points discussed in the above link:
Windows Phone IP Over USB Transport(IpOverUsbSvc) service is running
Phone name is already in use by this account
Too many phones have already been registered with your account
Device lockscreen has to be unlocked (and it is unlocked)
Can’t find any devices
Point 5 is also addressed in this answer https://stackoverflow.com/a/30303946/3956566.
Update after comment
The other thing that you may need to do is:
1. make sure you have all your updates in Windows.
2. Make sure you have all VS updates.
3. reinstall VS.
4. Reinstall any .net framework packages for VS.
The first two are the most likely things.
If worse comes to worse, to reinstall windows.
I have needed to do all of the above at one time or another to fix various issues. Painful, yes.
And don't forget to reboot your machine.
Let me know if this works. There MUST be a solution.
I know what you mean about the phone appearing in explorer, update anyway, won't hurt to reinstall them.
I'm experiencing a few issues with my APK when I run them through ARC-welder on OSX and so would like to verify whether these also occur in ChromeOS. Until I have a Chromebook is there a way to build and run my app in a Virtual ChromeOS?
I have Parallels and their ChromeOS set up, but the build is very old and I have not found a more recent version.
Or, do I just have to go out and spend some money on a Chromebook?
Thanks for reading