vBulletin Mobile Suite app rejected by Apple

[Trevor Hannant]

If you have crash reports, pleas raise a Bug under the vBulletin iOS App project here and attach the reports to that - this will then go straight to our developers for them to investigate:

http://tracker.vbulletin.com/secure/CreateIssue!default.jspa

[Moshe1010]

Thank you!

The query was iOS 6.1, not 6, though -- we know it works fine on ioS 6. iOS 6.1 was issued to users just a couple of weeks ago, although available to developers for the last few months. It's a requirement of Apple that any app be compatible with the current iteration of their OS.

Drink some water man, you're acting like crazy. vBulletin doesn't have to debug Apple's crappy software just because Apple has unlimited amount of bugs in its own software. That's not a secret that Apple already issued iOS 6.1.2 to its users in just less than two weeks. What company can handle a QA that can check every single iOS update in a week or two? Let me answer you: no company, even not Apple. People here are asking you to open a ticket so they can debug you issue and provide you, and maybe other users, a quick fix. You don't want to give any details to the people who should handle this kind of problems, and you keep complaining, which does not make your situation any better. So you can ask in the seventh, eighth, or hundredth time about a QA to iOS 6.1, and the answer would be the same: open a ticket. You don't want to open a ticket and provide all the necessary information? than it's your own problem. vBulletin wants to give you support, you refuse to take it - it's a given fact.

[Morrus]

Yes, the product has been tested on an iPhone 5 running iOS6.

Thank you!

The query was iOS 6.1, not 6, though -- we know it works fine on ioS 6. iOS 6.1 was issued to users just a couple of weeks ago, although available to developers for the last few months. It's a requirement of Apple that any app be compatible with the current iteration of their OS.

[Zachery]

Yes, the product has been tested on an iPhone 5 running iOS6.

[Morrus]

I need you to open a ticket so I can debug the issue, if you don't want to open one there isnt much we can do

There is one thing you can do. You can answer my question.

Are you refusing to answer my question? Seriously, dude, it's now looking like you're hiding something. This is the opposite of customer relations. You've been asked FIVE times now, and avoided the question every single time.

It's becoming a Monty Python sketch. Answer the question, please. If you've forgotten it, it's this (for the sixth hilarious time):

Has this product been tested on an iPhone 5 running iOS 6.1?

I'm not QA - I can't tell you what has been tested on what.

Then please ask "QA" and let me know the answer.

- - - Updated - - -

I've had a wonderful idea which might circumvent the mental block here.

As an exercise, imagine I haven't already given you my money. I'm a potential customer, considering buying your product. I have a question!

"Hey guys, your product looks great, but before I buy it I need to know if this product has been tested on an iPhone 5 running iOS 6.1?"

Does that help?

- - - Updated - - -

Well, Twitter is telling me at length that the reason my question isn't being answered is because the answer is "no". That does seem like the likely situation.

You might be wondering why I'm reluctant to hand over access details. Well, we're recovering from a recent devastating hack. We're rebuilding at immense cost in terms of workload and monetary value, and we're using a Kickstarter to fund it. We've raised over £30K so far, which is wonderful.

But part of that is that I will not hand over access details to *anyone* unless absolutely necessary. In this situation, it is not absolutely necessary.

So when you tell me you won't let me know whether your product has been tested on an iPhone 5 running iOS6 unless I give you my FTP details - well, let's just say that answering that question does *not* require my FTP details.

So please just answer my question.

[Zachery]

I need you to open a ticket so I can debug the issue, if you don't want to open one there isnt much we can do

[Mark.B]

I'm not QA - I can't tell you what has been tested on what.

Zachery has asked you to raise a support ticket for good reason. It isn't to be difficult, or awkward, it's so we can help you fix the problem.
It's the best way to fix the problem; that's the only reason.

Please help us to help you by supplying the details Zachery has requested.

Lots of people DO have the app working, so it's not that "the app don't work"; however clearly you're having difficulties so we need to help you resolve that, which is what we're trying to do.

[Morrus]

If you don't want to do that, we're not going to be able to assist.

This is untrue. You can assist; you are refusing to assist. There is no "not able to" about it, and I utterly resent your telling me so. You are perfectly able to answer the question I asked.

I am very concerned by the fact that you refuse to. Not because of what the answer may or may not be, but because you think it's OK not to do so.

Demanding answers to questions which may or may not be related to your problem, isn't going to get anyone anywhere.

It's going to get me the item of information I want. Please answer the question. It will take you less than 3 seconds.

To be clear..

To be absolutely-mofoingly clear: HAS YOUR PRODUCT BEEN TESTED ON AN IPHONE 5 RUNNING IOS 6.1?

Please just answer the question, dude. Please.

To be clear, if you refuse to answer a basic question about your product, tell me instead how I arrange a full refund.

Seriously, why is my interaction with you making me angry? I'm sure it's not supposed to make me angry. It is, though. I've spent a lot of money with you over the last decade. Don't make your customers angry.

[Mark.B]

If Support ask you to start a ticket, that's because we need you to do so in order to investigate what's going on. If you don't want to do that, we're not going to be able to assist.
Demanding answers to questions which may or may not be related to your problem, isn't going to get anyone anywhere.

To be clear: Please log a ticket with the information Zachery requested in post #3, and one of us will pick it up.

[Morrus]

Soo you started a ticket?

Dude, is there a problem with answering my question? You've ignored it twice now.

For the third time:

Has this product been fully tested by you as working on an iPhone 5 running iOS6.1?

It's a quick yes/no query. It doesn't require my being sucked into your support ticket system.

[Zachery]

Soo you started a ticket?

[Morrus]

Was your Android app also crashing?

Insted of <center>your text here<center> you can use:
<div style="text-align: center;">Your Text Here</center>
It resolves the issue.

Yeah, hasn't helped (see above).

I really need confirmation from someone that they have it working correctly on an iPhone 5 running iOS 6.1.

[Carbuff]

Not at all. Why?

Because that's such a silly thing to be a bug it sounded like you were making a joke.

Anyhow, OK I guess I can try removing the center tags and see if it makes any difference.

Was your Android app also crashing?

Insted of <center>your text here<center> you can use:
<div style="text-align: center;">Your Text Here</center>
It resolves the issue.

[Morrus]

Not at all. Why?

Because that's such a silly thing to be a bug it sounded like you were making a joke.

Anyhow, OK I guess I can try removing the center tags and see if it makes any difference.

- - - Updated - - -

Notice removed. I browsed it for a while and it didn't crash like before, but I've managed to get the menu to pop up and now the app has hung ... and as I type ... it's crashed again.

Can you please confirm that this has been fully tested as working on an iPhone 5 running iOS6.1?

[Zachery]

You're kidding, right?

Its unfortunately a known bug.