Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Beta software problems?

BarracksSi

BarracksSi

Suspended
Original poster
Jul 14, 2015
3,902
2,664
I know I've been here a little less than a year, but holy crap, guys...

How about this: When you encounter a bug or unbeknownst-to-you feature in beta or prerelease versions of the OS, and you want to start a new thread about it...

... you also mention the fact you're using beta or prerelease software in the thread title.

Does that make sense?

Most of the threads talking about broken or wonky software eventually end up with the thread starter saying something like, "It started when I installed developer release beta x.0.0.12.0.1.b."

Um... duh. Why can't the thread start with such necessary information?

What are they saying on Apple's dev pages? Did you also check Stack Overflow? What about swift.org? Did you check the error logs?

Cripes. I can only hope that the WWDC attendees are a little smarter about how to ask questions.

[/rant]
 
  • Like
Reactions: jgelin, chuyn, sean000 and 2 others
maybe you should find another forum that doesn't bother you so much you have to complain about everyone posting about their problems or concerns. If you enter someones thread and you don't have anything to contribute or are "upset" with their chosen format you should just move along....what are you 12...?
 
  • Like
Reactions: Newtons Apple
BarracksSi said:
See, now this guy knows how to write a thread title:

https://forums.macrumors.com/thread...ing-steady-at-about-1-hour-remaining.1977323/

It's fine. Basic software info right there at the top.

Now, oftheheavens, go back and check whatever you need to check, then send in a proper bug report. Let us know how you fix it.
Click to expand...

what are you talking about I have nothing to check I am now running beta on both devices. you really need to learn how to read before you post random bs
 
  • Like
Reactions: Newtons Apple
oftheheavens said:
what are you talking about I have nothing to check I am now running beta on both devices. you really need to learn how to read before you post random bs
Click to expand...

The OP isn't spouting random BS but has a very valid point. Many non-developers such as yourself who install non-public betas do not bother to at least state upfront that you're running a beta, leaving us scratching our heads until we find out down the line that you're running a beta. You did exactly that in a thread you started today.
 
JayLenochiniMac said:
The OP isn't spouting random BS but has a very valid point. Many non-developers such as yourself who install non-public betas do not bother to at least state upfront that you're running a beta, leaving us scratching our heads until we find out down the line that you're running a beta. You did exactly that in a thread you started today.
Click to expand...

My bad. I will take this into account as I find and post bugs. Thanks for your input without being snide like some others can be.
 
Here's the thing --

When a thread pops up to discuss a problem, whether it's hardware or software, I want to read it because either:

- I found the same problem and am looking for an answer,
- I already solved the problem myself and want to see if I can add anything to help, or
- I haven't encountered the problem yet and I want to learn what to do about it.

Two of those three reasons are, basically, trying to find help or information, not dish it out.

But when I start reading a topic and discover it to be badly worded or incomplete, or that the thread starter isn't giving useful information for the first two or three pages, I find the whole thread to be a waste of time -- not only for myself, but for the other forum members, and even for the thread starter.

It's really not difficult to state things clearly from the outset. Not doing so is a sign of either inexperience or laziness.

If you don't think you would describe yourself as "lazy", take an extra minute or two to write a post good enough for other people to understand.
 
JayLenochiniMac said:
The OP isn't spouting random BS but has a very valid point. Many non-developers such as yourself who install non-public betas do not bother to at least state upfront that you're running a beta, leaving us scratching our heads until we find out down the line that you're running a beta. You did exactly that in a thread you started today.
Click to expand...

oh and just to clarify, you stated I'm a "non-developer" and that is incorrect. I am attempting to develop an app, and have tried in the past but hit a roadblock and/or became busy with the military (now a medically retired Marine with more time on my hands) and now I would like to get back into learning how to do even the simplest of applications. I understand that a lot of the people here just buy the $99 license to have the latest to show of to their friends or whatever the reason may be but this is not the case here. Again thanks for the input.
 
oftheheavens said:
oh and just to clarify, you stated I'm a "non-developer" and that is incorrect. I am attempting to develop an app, and have tried in the past but hit a roadblock and/or became busy with the military (now a medically retired Marine with more time on my hands) and now I would like to get back into learning how to do even the simplest of applications. I understand that a lot of the people here just buy the $99 license to have the latest to show of to their friends or whatever the reason may be but this is not the case here. Again thanks for the input.
Click to expand...

Fair enough. The OP's whole point is it would be helpful if people state upfront if they're using a beta of any type, including iOS public beta while still on current wOS (as was the case with iOS 9 public beta and wOS 1). Bugs can go both ways.
 
No $99 license is needed to learn to write in Xcode and run apps on your own devices. Took me a full day in a weekend workshop to learn how to lay out and write a basic calculator app -- it doesn't even have an "equals" button, for cryin' out loud -- but I can finally say that I have my own iPhone app.

Speaking as one retired Marine to another, I'll say that coding isn't as hard as it looks from the outside. It's all just taking data, doing something with it, and giving an output. The syntax is the weirdest part. Go through some Swift tutorials with Xcode and get started.
 
BarracksSi said:
No $99 license is needed to learn to write in Xcode and run apps on your own devices. Took me a full day in a weekend workshop to learn how to lay out and write a basic calculator app -- it doesn't even have an "equals" button, for cryin' out loud -- but I can finally say that I have my own iPhone app.

Speaking as one retired Marine to another, I'll say that coding isn't as hard as it looks from the outside. It's all just taking data, doing something with it, and giving an output. The syntax is the weirdest part. Go through some Swift tutorials with Xcode and get started.
Click to expand...

Thanks
 
OP is correct. This is a great idea. Any thread that posts a problem/feater that is related to Beta should be auto-deleted unless "Beta" is in the title. Especially the thread referenced above, which gave no hint of beta until several posts in. That should be auto-deleted, and the thread starter should be digitally flogged.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back