Dyteq.com Corporate blog: Socialmedia. -marketing, -gaming, Flash, Flex and more

Two errors that cost us some time to figure out, hope Google lands you here safely…

Application failed codesign verification. The signature was invalid, or it was not signed with and iPhone Distribution Certificate
Unable to extract codesigning entitlements from your application
Not much info on this one because the normal iOS developers (with their xCode) don’t run into this one a lot.
We had a folder names “resources” with images that conflicted with the folder named “resources” that is in the final ios-package. So rename this folder to “assets” or something (and update your links!)

Exporting release build: Packaging for Apple iOS. This may take several minutes.
When you do a “fast” build for device testing, this will stay at 57%. If you want to “distribute” the app to the app store, this will just sit at 0% forever.
For us, there was an error in the p12 certificate. Make sure that the certificate in your Apple keychain access has a dropdown-arrow and that you export the correct item.

It’s on all the mayor sites, so you’ve already heard about this.

I think it’s a bad move. Here’s why:

The tablet-computer will replace the desktop computer as primary internet-device for consumers. Look at all the charts, tablets are outselling laptops. It’s just a matter of time.

Slowly but surely, Adobe will loose their 95% Flash-penetration and developers will stay away.

But Adobe know this, of course. So what is it they want from this?

Old trick I found while browsing some of my code:

If you have an array of Strings, you can get all the unique strings in just a few lines of code:


function array_unique_string($arr:Array):Array{
var o:Object = {};
for each(var s:String in $arr) o[s] = 1;
$arr = [];
for each(s in o) $arr.push[s]
return $arr
}


This function simply creates a temporary object with properties named after the strings in the array. A property is unique to an object, so setting it more then once will only change the value.
This gives us an object with all the strings from the array and by putting those back into a new array, we get an array with unique values.

You can use this for integers too:


function array_unique_int($arr):Array{
var o:Object = {};
for each(var i:int in $arr) o['_'+i] = i;
$arr = [];
for (var s:String in o) $arr.push(o[s]);
return $arr;
}


And Numbers:


function array_unique_number($arr):Array{
var o:Object = {};
for each(var n:Number in $arr) o['_'+String(n).replace(',', '|')] = n;
$arr = [];
for(var s:String in o) $arr.push(o[s]);
return $arr;
}


I have not benchmarked this, but I imagine some speed improvements when the array is long enough. Though I guess the substr and replace require a fair amount of CPU themselves.

According to this article, Ipads have already surpassed the Iphone when it comes to website visits.

Occording to this Chinese article, there will be a windows 7 app store.

There where some far fetched speculations of an app store for Windows 8 (based on the lawsuit that Microsoft and Apple got into over the name “App Store”). These screenshots, however, seem to be for Windows 7.

So, either a great photoshop, or a great leak.

You decide.

Handy little one-liner: Click the textfield to clear it. No need to write a seperate functions or anything.


<input name="email_address" value="Email address" onfocus="if($(this).val() == 'Email address') { $(this).val('')}" type="text">


Requires JQuery though.

The photo in this article (apparently) contains a part with the 30-pin connector for a sliding keyboard. I have to take these guys word for it, because I no speak Korean, sorry.

The apple.pro website has actually spread some rumors in the past that became true. This particular rumor fits in a strategy for Apple to release different types of iphone (iphone nano, iphone keyboard, iphone HD etc) to appeal to more consumers.

I use both the Iphone and the Andoird Desire Z (which has a full keyboard) and I have to say: I hate any kind of on-screen keyboard. I really do. I love the physical one.

A couple of months back I found a bug in Flash builder 4.

When you perform a native drag-and-drop and try to debug the drop-event, a crash would occur when trying to browse the variables in the debugger.

I kinda-sorta solved this at the time by tracing out the required data, but I felt bad for anybody that would run into the same thing.

So I posted a bug-report at Adobe.com.

I never did post a bug report on anything (usually to busy with handeling my self-created bugs… ) but it was an interesting process.

Adobe uses “JIRA” for their bug-tracking; a very feature-rich web application.

After posting the bug report, I was kept up-to-date with the progress of the bug by e-mail. I would receive an e-mail with updated status or added comments.

From this, I noticed that bug-tracking an application with the size of Flex builder is a pretty bureaucratic process. The bug was assigned to 3 or 4 different people and the priority changed a couple of times until it was finally marked as “resolved”. There is no futher info on how the bug was resolved or how the bug occured, that is a too bad because I was very curious. But it is nice to know that they take user input seriously and work to improve the product.

See the bug report right here.

Google revealed some details on the upcoming Android release through phonescoop.com.

To sum it up:
There’s a a new “action bar” which is located at the top of the display and can hold application-specific buttons. So my guess is that developers can customize these buttons through the app xml file.

The currently existing function of pressing the screen for a longer time to get additional options will be depcricated. The actionbar will take over this functionality.

An important note for all developers: Honeycomb is specifically for tablet development. In a later release, the Honeycomb branch will be merged with the Gingerbread (smartphone) branch. This merged branch will probably be the Ice cream branch and will be for both tablet and smartphone.

According to these two press releases, Nokia will release a line of Windows Mobile powered handsets. Is this part of the strategy change that was proposed in a leaked memo by the Nokia CEO earlier this week? The same CEO that worked for Microsoft not too long ago.

Part of this Microsoft / Nokia deal is a feature that allows users to pay for apps through their phone-bill. Something that was a longtime coming, we’ve been able to buy ringtones and wallpapersthrough our phonebill for years.

[source]