Welcome back to practiseSafeHex's new life as a manager.

Episode 2: Why automate when you can spend all day doing it by hand

This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:

- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.

- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.

- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.

- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?

- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.

- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.

*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.

and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.

- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.

... Heres hoping my head continues to not have a bullet hole in it by then.

Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.

And remember to always practiseSafeHex

I give up. It‘s impossible to argue with Apple.

I tried to bring my unofficial iOS devRant app "JoyRant" into the AppStore. It was available via TestFlight for years and it wasn‘t a problem there, apparently. Now for the AppStore, it is a problem.

I talked with the Apple review team for 3 weeks and the discussion went in circles.
They said that my app tries to disguise as or to misrepresent another app on the store (the official devRant app, even though it‘s not available anymore, apparently).

I was asked to remove all of the mentions of devRant from any description or any place in the app. I did. Even though it was stupid because how are people supposed to know that they need a devRant account to use my app? I‘m not allowed to mention devRant.

After that, they said that it can not have the name JoyRant because it sounds too similar to devRant.
I changed it to devJoy everywhere, the app, the meta data for the app store, the github page where the required legal crap is hosted, and in the legal documents themselves.
Did it help? No, it didn‘t.

Apple then proceeded to claim that my app is trying to deceive the users into thinking that this is the official devRant app. Even though I have explicitly stated in the description that it is just an unofficial devRant client.

Now apple says that I should "revise the app content".
Which I assume means that I need to make it something different. Yeah. Great suggestion!

So, I will rename the app back to JoyRant and provide it via TestFlight, as it was before.

Thanks for reading. I needed to vent.

I hate people who think that building software is all about one click away and generating things. I got told to complete the task faster than the speed of light.

Fancy me some rant time? Let's name that cunt, "Bob".

"
Hey Bob, I got questions for you. Are you sure you were in your mum's womb for 8-9 months? Are you the kind of twat who honk at people as soon as the traffic light's turning green?

Building software takes time, the CI/CD takes time, TestFlight takes time, approvals from the Google Play store take time, approvals from Apple App Store connect take time, Unit testing takes time and every fucking thing you can name takes time!

It's just like sex, nobody wants to be with someone who can only last in bed for 0.000000000001 nanoseconds, the longer, the better, (but not too long).

It is also like building houses, which takes months to build not hours. As from my experience so far, something tells me that you are not the kind of person who would understand how to build a house but a sand castle which takes only hours to build.

Relentlessly, you bombarded me with a pile of bollocks and a pile of nonsense is not going to fasten up the compilation of the software.

"

After 8 iTunes Testflight Beta approvals for my app ... better still, I got hte app approved for the App Store a week ago to "de-risk" our "final submission" ... That's 9 approvals for my app, and we're ready to submit version 1.0.0 and actually release on the store. We take last week approved app and "developer reject" if to make room for the final tweaked version (minor tweaks, minor bugfixes). Submit version 1.0.0., plenty of time before it needs to be released.

But, what's this? "Meta Data rejected" for v1.0.0 because some piece of shit at Apple wants to watch a video of the app working with our hardware. What about the previous 9 approvals with the demo account connected to the demo hardware?

So we send a video within 1 hour of their unexpected request about the very foundational fucntionality of our app. That was 24 hours ago and these fucking assholes haven't even responded, no sign of when they will trouble themselves to respond. Pure limbo.

All the work up to this point was to "de-risk" their infamously shitty review process and all of it was in vain because it's somehow brand new information that our app works with our hardware.

Holy fuck, what a bunch of power-tripping assholes. All I can do is pace around and review the previous 2 months in my head to figure out what I could have done better. But I could not possibly have expected that after all the Testflight Beta approvals and after the recent App Store approval, that they would suddenly doubt that our software actually works with our hardware!!!!!

FUCK YOU APPLE!!!! FUCK YOU WITH ALL MY HEART!!!!!!

Good news!

I recently found a job at a call center for a local Japanese food joint, and I will finally get enough money for a paid Apple Developer certificate, and now I will be able to publish the app on TestFlight, have proper notification services, etc! I will update you on the situation.

!rant

FUCKING FINALLY

I GOT THE APPLE DEVELOPER CERTIFICATE

PUBLIC TESTFLIGHT PARTICIPATION SOON

THIS IS SLAMMIN

!dev !rant

Personal life update:

Like I said a few rants ago, I got a job in a call center for a national Japanese food chain. I am getting a pretty good salary for a teenager, and I am being paid the same amount as the other call center agents.

What I didn’t tell you is that I am doing a pre-university SAT, and it’s pretty much destroying me. I regret choosing to do it.

About AltRant: currently on short hiatus, though I swear to god that I will DEFINITELY upload it to TestFlight so you can get a taste of the app. All I ask is patience. I think I will wait until iOS 15 is out because the latest betas created a massive issue in a few parts of the app. All of them are aesthetic but damn it, I want to fix them only when they are officially there to stay because right now iOS 15 is still in beta.

I don't know if our QA is good enough. We were developing an app for both ios and android. I, an ios developer, told the QA guy that it will take long before uploading the app in the testflight (convert swift2 to swift3). After a week the app is now uploaded in the test flight and at the same time my partner, an android developer, uploaded the android version of the app in the play store beta. The QA guy started to raise bug issues about the android version. He wanted to fix the bugs immediately since our boss needed to upload it in the play store and appstore. The QA guy kept on complaining to my partner why the android version is buggy. Then he said something we, me and my partner, facepalm.

The QA guy said " You shouldn't convert the app to swift 3. The ios version is fine when converted why the android version is buggy. You need to revert it back to swift 2"

We sit there in silence, thinking if we pity the QA guy or laugh at him.

!rant

I finally returned from my hiatus, I am starting professional college now and I am starting to work a little again on AltRant! The next feature will be weekly rant group support. I am unsure about when it will be released to testers on TestFlight but it will be pretty soon I think.

!rant

My mobile game is going live soon, but I need beta testers to give me feedback about the game. It’s a simple mobile game, think Ketchapp style. If you’re interested in testing and have an iPhone (😱), please either contact me here or on my website or wherever so I can invite you to TestFlight. Thanks!

It is day 4 since I started trying to export my Flutter app for iOS. I am finally at TestFlight point.
This....
has been.....
....exhausting.

Achievement complete: have an app approved for TestFlight. Next goal: release to App Store.

Mobile Dev...
What I wish I did: Writing a new pod to allow connectivity with your smart glasses to profile dangers while driving.
What my PM wants: Update the color on the sign in button
What I really do: Take three hours to install pods and build the testflight for the client

I just released a new version of AltRant for TestFlight users, it’s supposed to fix most issues about the home feed layout. All testers are asked to update and test.

I can build my .aab, upload it, have it approved, and release it on Google Play before my stupid .apk IS EVEN DONE PROCESSING ON APP STORE CONNECT

WHAT ARE YOU DOING APPLE FIX YOUR STUPID S3 BUCKET OR WHAT THE HECK ARE YOU DOING WITH THE BUILD THAT IT TAKES SO LONG TO EVEN GET IT IN TESTFLIGHT AAAAAAAAAA

AltRant update:

Slight detour in plans, I will have to postpone any and all updates for AltRant until I finish both final projects in college this year. However, I will keep the app afloat in TestFlight for testers to keep using on a daily basis.

Why xcode and ApplicationLoader sucks?
Everytime I've to upload IPA to testflight/store, xcode and AL would fail 100 times before successfully uploading one.

JoyRant beta has expired! Need new TestFlight link

What is the best way to install iOS app for employees in a company?

Disclaimer, I'm no iOS developer.

In 2019 my boss asked if I could make a small iOS app. 3 forms which will have CRUD operations. I did it because I wanted to learn iOS development. The company got an Apple Developer Account and it finished the project within the week. The app can be used only from work's wifi, so if you try to use it outside that network will not work.

The issue is license. When I install the app from my XCode to one of the employees' iPhone, the app will work for 1 year (if I have paid for Developer Account). Also every time I make an update, the employee have to come to me with the iPhone and I have to install it directly.

Yesterday I submitted the app for Testing using TestFlight. The app updates automatically, but today I got notification that the "Submission for testing is rejected", because the tester could not connect with the server.

My question is, How do you install iOS apps for your work employees? I do not want to get Enterprise account because that will cost.