Pocket Habbo version 1.0.6

[dominic]

I'm in the need of the IPA for Pocket Habbo version 1.06 (iPad version 1.06)
If anyone knows that they have it, please send it to me!

[MentaL]

[Drkley]

Just sync your ipad apps with itunes and get it from the folder it stores the ipas.

[dominic]

Just sync your ipad apps with itunes and get it from the folder it stores the ipas.

It's an old version and therefore not longer available :(

[Drkley]

It's an old version and therefore not longer available :(

So you need it for the old discontinued app ?
Here i found v 1.0, maybe not exactly useful but sharing doesn't hurt.
https://mega.nz/#!8wJnCC4A!WipFQsq7O...U1hnruNI0vbVSY

[dominic]

So you need it for the old discontinued app ?
Here i found v 1.0, maybe not exactly useful but sharing doesn't hurt.
https://mega.nz/#!8wJnCC4A!WipFQsq7O...U1hnruNI0vbVSY

Sorry, should have been more specific!
It's the iPad application where you can actually load the hotel..

[Droppy]

Sorry, should have been more specific!
It's the iPad application where you can actually load the hotel..

I don't get it... Don't you mean Habbo Air?

[dominic]

I don't get it... Don't you mean Habbo Air?

Yep i do

[Droppy]

Yep i do

Might not have ipa, but the .swf which is used inside...

I've done a few tests on hAir, and I think it's worth a try to only insert .swf on IPA...

[ovflowd]

Habbo Air is really hard to make an Emulator for Android/iOS version.

Some points:

1. The Releases are totally different from Desktop Version
Habbo regularly update his SWF, and every time run's his Encrypt Algorithm. Obfuscating all, and removing imports, and renaming all variables, voids, etc with weird names. (Only some things isn't obfuscated, every release is some different things that have a clean name - depend the release)
Other thing is all Packet Id changes. Every build, you know it.

2. Habbo Air doesn't use Habbo Desktop Branching Build Names (RELEASE, PRODUCTION, DEVELOPMENT) (Obviously i mean they doesn't use the SAME releases in Desktop <-> Air) First because all the Action Script is basically different (In terms of Visual Objects).

3. Habbo Air of iOS has same "RELEASE" of Habbo Air for Android, but the Engine is totally different.

4. Is really hard make a unified Habbo Emulator for Desktop <-> Tablets/Phones, because of the structures and id's are different. Is not impossible, (because Habbo has) but is hard.

5. A lot of other things, like only cracking the SWF from Habbo Air isn't sufficient for play in "retro" servers. The Port and Ip-Address must be injected manually for each Retro and build each app in Android SDK. (The ARM code is lost when you try force a inject without build)

6. Android only connects to SSL Servers, Must have Android Developers "Certificate" (if you want to put in Play Store, also to Android connect must also a "recognized" connection (if you don't have root in phone).

7. Apple and Google can ban your developer access if Sulake reports. Is really a lot more easy your ben jailed with that, than Normal Habbo Retro. (Because you accepted Google and Apple Developer license...)

8. Other things, that Droppy can confirm or continue.. (Also the Encryption Algorithm is totally different.)

[dominic]

Habbo Air is really hard to make an Emulator for Android/iOS version.

Some points:

1. The Releases are totally different from Desktop Version
Habbo regularly update his SWF, and every time run's his Encrypt Algorithm. Obfuscating all, and removing imports, and renaming all variables, voids, etc with weird names. (Only some things isn't obfuscated, every release is some different things that have a clean name - depend the release)
Other thing is all Packet Id changes. Every build, you know it.

2. Habbo Air doesn't use Habbo Desktop Branching Build Names (RELEASE, PRODUCTION, DEVELOPMENT) (Obviously i mean they doesn't use the SAME releases in Desktop <-> Air) First because all the Action Script is basically different (In terms of Visual Objects).

3. Habbo Air of iOS has same "RELEASE" of Habbo Air for Android, but the Engine is totally different.

4. Is really hard make a unified Habbo Emulator for Desktop <-> Tablets/Phones, because of the structures and id's are different. Is not impossible, (because Habbo has) but is hard.

5. A lot of other things, like only cracking the SWF from Habbo Air isn't sufficient for play in "retro" servers. The Port and Ip-Address must be injected manually for each Retro and build each app in Android SDK. (The ARM code is lost when you try force a inject without build)

6. Android only connects to SSL Servers, Must have Android Developers "Certificate" (if you want to put in Play Store, also to Android connect must also a "recognized" connection (if you don't have root in phone).

7. Apple and Google can ban your developer access if Sulake reports. Is really a lot more easy your ben jailed with that, than Normal Habbo Retro. (Because you accepted Google and Apple Developer license...)

8. Other things, that Droppy can confirm or continue.. (Also the Encryption Algorithm is totally different.)

It isn't needed to replicate the application, if we did find this, we'd be able to pull most of the source out of it - non obfuscated

[Droppy]

Habbo Air is really hard to make an Emulator for Android/iOS version.

Some points:

1. The Releases are totally different from Desktop Version
Habbo regularly update his SWF, and every time run's his Encrypt Algorithm. Obfuscating all, and removing imports, and renaming all variables, voids, etc with weird names. (Only some things isn't obfuscated, every release is some different things that have a clean name - depend the release)
Other thing is all Packet Id changes. Every build, you know it.

2. Habbo Air doesn't use Habbo Desktop Branching Build Names (RELEASE, PRODUCTION, DEVELOPMENT) (Obviously i mean they doesn't use the SAME releases in Desktop <-> Air) First because all the Action Script is basically different (In terms of Visual Objects).

3. Habbo Air of iOS has same "RELEASE" of Habbo Air for Android, but the Engine is totally different.

4. Is really hard make a unified Habbo Emulator for Desktop <-> Tablets/Phones, because of the structures and id's are different. Is not impossible, (because Habbo has) but is hard.

5. A lot of other things, like only cracking the SWF from Habbo Air isn't sufficient for play in "retro" servers. The Port and Ip-Address must be injected manually for each Retro and build each app in Android SDK. (The ARM code is lost when you try force a inject without build)

6. Android only connects to SSL Servers, Must have Android Developers "Certificate" (if you want to put in Play Store, also to Android connect must also a "recognized" connection (if you don't have root in phone).

7. Apple and Google can ban your developer access if Sulake reports. Is really a lot more easy your ben jailed with that, than Normal Habbo Retro. (Because you accepted Google and Apple Developer license...)

8. Other things, that Droppy can confirm or continue.. (Also the Encryption Algorithm is totally different.)

About the 8: it seems that it has changed basic stuff, not as a whole..

And you can use DNS/hosts file to emulate it,.. but seems pretty hard to replucate/crack it.