This Week At Hyperoid, we are facing more difficulties than expected.

TL;DR

Alright, before we get into this post, I’m just going to say that this post is going to be a short one. But I’ll give the TL;DR here if you want it. This week I managed to get a successful Android build up and running, however the same cannot be said for an iOS build, which is still being worked on. Being able to publish the apps onto their respective stores is facing some issues with verification and a lot of shenanigans regarding requirements. For this reason, the demo release is going to be delayed until mid March.

Demo Build Stability

In the last TWAH article it was stated that demo build stability was being worked on. This is still the case. It’s halfway there but there are things that still need to be fixed.

An Android version of the demo has been successfully built. The game runs as expected and doesn’t crash unintentionally. Which is good. I found it much easier to build for Android than iOS that’s for sure.

However, the same cannot be said for an iOS build. This has been very frustrating for me as the building process for iOS requires more equipment and software than it does for Android. At least that’s how it is for me. With Android, I can just make a build in Unity (after fixing any build errors) and test it straight on an Android device. But with iOS, I need to make a build in Unity (after fixing any build errors), build the game on another piece of software called Xcode (after fixing any build errors on this as well) before testing it on an iOS device itself…

As you can see, the process of building and testing on iOS seems to have some extra steps. Not to mention the build errors I have to fix both in Unity and Xcode then having to test if the demo does not crash on top of that.

The App Stores

In order to publish to the Apple App Store and Google Play Store, I needed to setup developer accounts for both platforms. This I managed to do, but was hit with some obstacles. 

For starters Google asked me for some verification documents for an organization. This was confusing to me because the developer account was made to publish apps under a single individual, so why I was required to do this was beyond me. I have contacted Google support on this matter and am eagerly waiting for a response. 

Secondly, I am trying to wrap my head around all of the requirements and settings that need to be configured in order to publish to the Apple App Store. I’m already having a hard time building the demo for iOS, it only makes sense that trying to publish to the Apple App store is going to be another pain in the buttocks…

Closing Thoughts

Feedback streams and a Kickstarter campaign are still in the works. When they are close to completion, be sure to expect some news on that here.

I did say that the demo was set to be released in late February. Well that time has arrived so quickly and I once again did not anticipate the hurdles I am going through right now. All I ask is that you bear with me while all of this gets sorted out. Once that iOS build is up and running, the demo will be well on its way to the app stores. Thanks.

“This is Hyper, signing out.”

Hyper