We use a custom Air Install badge to install / launch an Air application directly from the website simillar to
TweetDeck
This normally handles the install of air if the user doesn't have it already installed.
However, after doing some cross broswer testing, it appears that when a user, (using OSX Lion and Safari or Firefox) tries to click yes when prompted to download the required Air they are unable to click either of the yes or no buttons.
Has anyone experienced this issue or know of any solutions or work arounds?
I initially thought that it may have had something to do with the positioning so ensured that the z-index in the css was appropriately set but to no avail.
I beleive it may have something to do with the installer itself rather than my implementation as the same thing appears to happen on TweetDeck too.
Yeah, I've run into this issue before. The workaround we found was to restructure the html/css so that no ancestor of the badge uses margin: auto.
It turns out that the issues was due to the version of FlashPlayer that the browser was using.
By upgrading FlashPlayer, the badge functions correctly on Windows, however on OSX there still seems to be a bug where, if you do not have Adobe Air installed, it will not ask if you want to install the Air runtime and it and will proceed to install the application anyway - resulting in the install failing.
As of writing the latest FlashPlayer version was 11.x
Related
Anyone try using Microsoft.Identy.Client package with Xamarin.Forms in MacOS project?
I try to implement OpenUrl method according to sample: https://github.com/Azure-Samples/active-directory-xamarin-native-v2/tree/master but in AppDelegate in MacOS project VS cannot see AuthenticationContinuationHelper class. Microsoft.Identity.Client class is limited:
Microsoft.Identity.Client in MacOS Project not show all items
At .Droid and .iOS project everything work properly.
Anyone was handled with this?
So there is a video from Build 2018 as well as the Slide Deck that discuss that. You need to make sure in your nuget settings you have the "show pre-release packages" checked, and then install the Microsoft.Identity.Client. I had the same issue until I did that, installed the nugets, cleaned and rebuilt the solution.
The problem with Xaramin.mac is that the library does not currently, nor does it sound like it will any time soon support the Xaramin.mac platform. This is mentioned in Open Issue #522 on the GitHub repository, after some further reading into it. That was dated on February 20th, with no news since then, so I don't believe they have it on their roadmap. Must be something with the way MacOS handles the brewer handoff, let alone the MacOS was just recently supported by some of their services in Azure, which makes me think there is not enough market share there yet in this space?
I was running my application from Flash Builder 4.5.1 without any issues. (It is a Flex application that connects to .Net Web Services). However, something has changed recently in my configuration or project, because when I try to run the app with the play or debug button, I just get a grey screen. I can't even stop on any breakpoints.
Eventually (maybe 30 seconds), a message pops up like so: 'The Flash Builer failed to connect to the running application. Please make sure that you are running the debug version of Flash Player...'
I definitely have latest version of Flash Debug Player installed (11.1.102.55). I have tried uninstalling it and re-installing it.
I have tried cleaning and rebuilding my project.
I have tried switching to a different workspace and back again.
I have tried restarting the PC.
I am using the latest version of IE for testing.
I'm really stumped - has anybody got any ideas on how to solve this?
Thanks
Have you tried deleting the html-template folder? This has caused issues for me in the past.
After it's deleted, when you try to build you will have a compiler error/warning about the missing folder. Right click and 'rebuild'.
There are some issues with compatability between 64 bit IE9, the 64-bit flash player, and 32-bit debugger. It seems like flash builder gets confused on which to use. I haven't seen any decent resolution yet in the Adobe forums for this particular issue other than use a different browser for testing.
To switch browsers, go to Window > Preferences... > General > Web Browser in Flash Builder. Select Firefox or Chrome.
In order to use Firefox, you need the Flash Debugger for Netscape compatable browsers installed. You can get that from Adobe here.
To use Chrome, you need to replace the built in flash player that is installed with Chrome with the debug player. Instructions from Adobe are here.
This is the message while trying to run under XCode 4 (it used to work under XCode 3):
No provisioned iOS devices are available. Connect an iOS device or choose an iOS simulator as the destination.
I have profiles for my device for this app... where should I be looking to correct this?
The problem is that your iOS Deployment Target in Project-> Build Settings is different from the current version of iOS on your real device.
You're asking where to find it:
In XCode 4 there is a new button - look for the big
"Organizer button"
which is at the TOP RIGHT.
Physically connect your device and then click Devices. It seems that the new "Organizer button" is one of the "most-missed" things in the transition to XCode4.
Note, the questioner is asking: "WHERE should I be looking to correct this?"
I was having extra trouble because of my Enterprise License, but still updated the iPads. I didn't have to change anything in the Build Settings to lower. But the main thing that I had a problem with was in the Organizer I needed to hit "Use for Development" button.
Kind of an old post, and may not be the best way or a rookie thing to miss but wanted to help anyone out.
My problem similar to those above were related to having the deployment target set too high for the version installed on the phone. Would be nice if it gave a more useful error message. I spent hours messing with my provisioning profile trying to fix it, when the real problem was the older version of the software on the phone.
I had the same problem. The reason was simply, that my ipad had not been update to version 4.3.
This just happened to me for iOS5 with xcode 4.2.
The answer is to go into organiser, select your device, and press the "Develop with this device" button (or similar wording).
Then go back and build, and it should work..
I received this error while having an iPad properly connected.
Some info:
Ipad iOS version: 4.2.1
XCode 4.2
XCode project created with "iOS Application / Empty Application" template.
The problem was that I had to specify the "iOS Deployment Target" to 4.2 in more than one place!
That is, both in the "Build Settings" and in the "Summary".
Very odd, and definitely another XCode4 annoyance.
I got this error in Organizer - "Could not support development.". I tried rebooting the iOS device and it worked for me :)
Check that the Executable File (also known as CFBundleExecutable) in the Info.plist file is set to ${EXECUTABLE_NAME} as opposed to any hardcoded value. This will ensure that even if you change your project name or target name or scheme name, that it still works.
you need to install the proper version of iOS.in my case it is iOS 4.0 - 4.1 Device Debugging Support
GOTO --> XCode Preferences -> Downloads --> Component
there are all updates available for your iOS click Install.
This is works for me.
It looks like this error can also come about if the "Product Name" in your target's build settings does not match the value of "CFBundleExecutable" in your info.plist
It looks like to me this is the general error Apple gives if the executable is not installed correctly on the device. When the debugger tries to attach it looks for the executable name and if it's not there they give this error. Touch one to debug.
Go to build option and select valid compiler.
Chose your right iOS Deployment version
I have installed flash player 10,1,82,76. When i tried to debug my application, it returned this alert message ..
C:\WINDOWS\system32\Macromed\Flash\NPSWF32.dll
Flex Builder cannot locate the required debugger version of Flash Player. You might need to install the debugger version of Flash Player 9 or reinstall Flex Builder.
Do you want to try to debug with the current version?
And When i tried to install flashplayer_10_ax_debug.exe, i got this message.
"The version of Adobe Flash Player that you are trying to install is not the most current
version. Please visit the Player Download Center to obtain the latest, most secure version."
What is the solution ?
What browser are you targeting? You may need to disable/remove the current version before continuing with the debug player install. I went through this process before for testing diff player versions (9, 10) in IE, Firefox and Chrome, and detailed it here
I had similar problem when I was trying to debug my application with an internal Eclipse web browser. When I changed preferences so that debug started in external web browser like Firefox or Opera, problem disappeared.
Hope that it'll be of any help to you.
Flex 3 debugging not working with FIREFOX 3 (under vista)
no trace() shown in console. breakpoints not working.
Do you have Flex Builder installed? If not, if you are using the free SDK, did you install the debug version of the Flash player?
Try reinstalling the debug version of the Flash player. Here's a link, in case you didn't. I had the same problem a week back -- corrupted my install. But also check out the config files as suggested in the other answer.
It worked perfect after installing the debugger from the link given above.
The exe that should be installed is listed as "Download the Windows Flash Player 10.1 ActiveX control content debugger (for IE) (EXE, 2.72 MB) " in http://www.adobe.com/support/flashplayer/downloads.html.
Do you have:
ErrorReportingEnable=1
TraceOutputFileEnable=1
In a file called mm.cfg in your home directory? I'm using FF3 on Windows Server 2k3 and it works fine, so I can't speak to why it wouldn't work on Vista. Despite Vista's reputation for being broken, I doubt that this is a Vista-only problem you're experiencing. You're sure you've got the debugging flash player installed?