TBD event.
It’s probably just a empty slot for future purposes. I assume it’ll be filled sometime during season 2, if they actually introduce a new zone.
Why not just either leave it as TBD or disable it. Personally, I don’t include unknown events and instead, use an updateable list while also allowing the user to insert their own. Don’t just hardcode it, because there’ll be even more added in the future, as well as temporary ones.
I agree whit u on the dynamic sistem. But i was wondering if TBD would be important on release. I need to send the app asap and will do this statically and add the dinamicly dolodable stuff in a few weeks.
You’ll probably want to remove the app from the App Store by April 15th, since the established APIs will no longer be relevant after that, and update accordingly. Afterwards, you’ll need to evaluate the API changes in relation to your app. It’s all pretty common sense stuff.
Do you use, or have looked at, GW2Kit?
You’ll probably want to remove the app from the App Store by April 15th, since the established APIs will no longer be relevant after that, and update accordingly. Afterwards, you’ll need to evaluate the API changes in relation to your app. It’s all pretty common sense stuff.
Do you use, or have looked at, GW2Kit?
The app will be updated in whole. Maybe there will be a day + but i will notice the user. Not shure how long the waiting time is atm for apple. I will not rellease uncofirmed stuff. Yust wondering if there would be something special to include. I agree that the apps should be done right.
TBD is Mordremoth, ofc….