Cocoa WebView SWF - objective-c

I am trying to load an SWF inside a WebView in my cococa app, it works fine when I load an HTML which references the SWF. But i'd like do load the flash file alone, with no HTML. Is that possible??

Yes.
It's broken in currently-released WebKit (even on Snow Leopard), but last I checked, it was fixed in WebKit nightlies, so it'll work again someday.

I finally found an answer for that. It is not quite a fix, but it can get my app working for now.
Every time swf is loaded it make a call to debugger and XCode stops.
According to this post, I should disable the option "Stop on debugger" at run menu in XCode.
Now my project is up and running.
Thanks!

Related

Active X VLC Plugin Issues

Im using a very basic ActiveX VLC Plugin. I installed VLC and then added VLC into VB.NET by going into COM Components.
So I use it to load livestreams and it works "fine".
But not great. The reason im saying this is because I load a .m3u8 file and whenever it lags/buffers/freezes/pauses e.t.c it will play again fine as I have it to "AutoLoop = true" but when it then fixes itself and continues playing it wont go Fullscreen by double clicking the Video Window and if I went into Fullscreen before it froze I would be Stuck in fullscreen and would need to ALT+F4 or ALT+TAB out and close the App.
Is there any way past this and has anyone ever encountered this issue either?
If anyone needs to try this to see what I mean or has a hard time understanding what I mean just let me know.
I can confirm this is an error with VLC 2.2.2
It seems this is a UI issue when playback ends. The forum seems to already have a ticket open about this for 3+ months which is ridiculous that its still not fixed.
If you compile using the .dll's from VLC 2.2.2 but have VLC 2.2.1 installed on your PC then this issue is gone.

How to disable phonegap autoreload (At least during dev)

Here is my issue:
I've installed phonegap and phonegap desktop.
http://code.riffzone.net/phonegap-install-msw/
Now, when I'm working on my application (Jquery Mobile), I'm testing it on a browser, but the application is reloading again and again after every 2 seconds and I can't even write something in the form input, reloading to fast..
I don't understand where this is coming from?
Here is the screen shot of my browser and the firebug console where you can see the page reloading over and over (1) and the api_auto_reload in the console (2).
Thanks a lot :)
The reload should be triggered only when some of your source files is changed. For some reason it does detect change on your files constantly. That reason is quite hard to find out without debugging more. You can, though, turn the auto reload off with --no-autoreload switch for phonegap serve like this
phonegap serve --no-autoreload
It was phonegap desktop beta (the minimalist server) and not phonegap (command line) which was causing this bug.
If you have the same issue, make sure you are not using it.

Application stuck at "Powered by Titanium screen"

I'm trying to run an app made on Titanium in my cellphone. At first it was working fine, until i decided to debug my code. After that whenever i try to run it on my cellphone, it gets stuck # the powered by titanium screen (that red one).
I tried to delete my build folder as some people said after a bit o research but it won't work.
How can i solve this?
What I would try to do is:
clean the project (it also deletes the build folder, but I think it also cleans some more stuff in there).
when the app starts try to set an alert in app.js as the first thing - see if this alert shows, and if it does - move it to the next step until you find a place where it is no longer shown which might indicate that this is where you problem is.
Look at the device logs - if it's an android device open ddms and look at the logs while you run the app - see if anything pops up. If it's an iPhone on xCode you have some sort of console viewer for the phone (sorry - can't remember the name right now).
make sure you are not still running under debug mode.
BTW - you didn't mention if it happens on iPhone or Android? does it happens on the simulator as well?
I was having the same issue. From digging through Appcelerator's Jira I found we weren't alone, and also got a workaround that allows us to get past the splash screen. Check to see if there is a deploy.json file located in your application's directory on the device. If so delete it!
Here is more info on the issue https://jira.appcelerator.org/browse/TIMOB-16086.
It's rated as a high priority to be corrected for the 3.3.0 SDK release.

My website crashes Safari (both desktop and iOS) consistently

My website http://remotejobs.io crashes Safari consistently. I first noticed the crash last night when I was at a Verizon store and I tried browser testing the site on an iPad. So I tried 2 more iPads at the same store, and the site crashed iOS Safari on all 3 devies, every single time I tried to hit the domain.
The exact workflow is:
Open Safari
Enter http://remotejobs.io
That's it. As soon as you hit go the site crashes.
This also happens on desktop Safari (tested in 6.0.3 on OSX 10.8.3 only), and produces an error report every time. Here's a copy of one of the error reports generated: http://go.jag.is/OGcS
The site is not throwing any JS errors, and works fine on other modern browsers that I have tested, including Chrome, Firefox, and even IE9 (shockingly enough).
One strange thing though, is that it only seems to crash iOS Safari on iPads, not iPhones, as I can successfully load the site on my iPhone every time.
What on earth could be causing this, and how do I debug it?
UPDATE: I tried commenting out the main stylesheet, and the site no longer crashes Safari without that stylesheet. I tried both a regular stylesheet, and a minified stylesheet, and both crash the browser.
UPDATE 2: I narrowed it down to the CSS by commenting out JS and leaving CSS in, and still it crashed. Then I tried removing all the transition properties, and it no longer crashes. So apparently the transition properties were causing the crash.
So I was able to narrow the problem down to the CSS with Adam Moore's suggestion, and then to the transition property declarations with Jonathan Sampson's comment.
I removed all the lines with transition and the site no longer crashed.
So then I looked at the values, and tried unifying the duration values, to see if that would help, since I was setting several different duration values across the different properties, including .5s on one, .3s on another, and .25s on yet a couple more. But unifying them didn't affect anything - still crashed.
Finally, I tried changing the transition-property from all to color, since color was the only thing I was really changing, and no more crashes! So apparently that was the solution. Seems Safari was choking on trying to transition all the properties.
Your website does not seem to crash Safari 5.1 on Windows 7. To go about debugging what's causing the issue, start by turning off the CSS, then one by one disable JS files until the website stops crashing. Once you've figured out which CSS file or JS file it is, then post a link to the file and I'll see if I can help!
I stumbled across the same issue in Safari and tried everything mentioned here. I also checked the css in the CSS validator and fixed some issues.
But my trigger for the crash were padding with percentage values. I converted the %-Values from the paddings and all the things were fine.
-webkit-transform-style: preserve-3d !important;
Caused Safari to continuously reload because of error. Removed that and it worked. :).
Safari - Version 8.0.8 (10600.8.9)
OSX EL Captain

PhoneGap InAppBrowser not loading pdf

I am using PhoneGap InAppBrowser to load pdf in my app. It is loading pdf in IOS, but there is no location bar shown, and on Android pdf is never loaded.
Here is my code to load pdf
iabRef = window.open('sample.pdf', '_blank', 'location=yes');
Not sure if this counts as an answer, but I believe this is a known bug. It is marked as fixed in the 2.4.0 RC here.
Ran into the same with 2.4.0. I switched to using the _system browser in my open call. It's not ideal, as it opens a browser that simply downloads the file, but at least it works.