Google Analytics Reports 0 Visits
This worked aafter I installed the app and hasn't worked since.
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solutions from the company
-
1.3 update is out, which solves this bug. Thanks for your patience, everyone!
The company says
this solves the problem
-
Updating this to "working on it" until Apple approves 1.3. So there's no confusion.
The company and 1 other person say
this solves the problem
-
Please look at the other support issues, since you ignored two open support requests with this same issue and two announcements.
This is fixed in version 1.3, already submitted to Apple and awaiting approval.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Please look at the other support issues, since you ignored two open support requests with this same issue and two announcements.
This is fixed in version 1.3, already submitted to Apple and awaiting approval.
The company says
this solves the problem
-
Inappropriate?Oh, I'm supposed to read all the other support requests marked "this problem is resolved?" sorry. It's still not resolved for me.
I’m amused
-
No, you're supposed to read the company response that explains WHY we consider it resolved. Which, if you had, you'd see that we fixed this issue in version 1.3 that was submitted to Apple last week and is awaiting approval. -
This comment was removed on 04/21/09.
see the change log -
Automatt: the whole point of Get Satisfaction is to provide a space for companies to answer questions publicly, enabling other users to find the answer to their question quickly. It's essentially an organic FAQ builder that saves everyone time. Take 10 seconds to scan through previous questions, or search for your issue. -
Thanks Robbie, I was browsing GS from my phone and that may have made me a bit myopic. -
Inappropriate?Updating this to "working on it" until Apple approves 1.3. So there's no confusion.
The company and 1 other person say
this solves the problem
-
Inappropriate?Thanks, that seems a lot clearer to me. I probably should have read your announcement from the beginning. It does seem odd though that "resolved" should be taken to read as "resolved, from a development perspective, but not for the customer."
Hopefully Apple will approve your new version in the next few days. Sorry you didn't like my review in the App Store. I also posted a review here:
http://www.rateitall.com/i-1986430-eg... -
You are behaving like a petulant child. Any rational person would understand, with minimal reading, that the quickest route to fixing the problem was taken. The issue, the reason why you were "berated" (read: instructed on the rules of this website), is that you acted thinking only of yourself, not of everyone else experiencing this problem. Garrett has been more than polite in dealing with you.
Why do you insist on creating a problem where there is none? The fact you have posted yet another vengeful review proves that you are unrepentant, even given your acknowledgement that you made a mistake in dealing with this scenario.
Swallow your pride, and start acting like an adult. -
Inappropriate?I used to work for a software company, so I'm very sensitive to such situations.
Personally, I think you should remove or modify those reviews, as they do not accurately reflect the situation. The developer posted announcements, and responses to others with the same issue, and informed you he had already done so. You've just admitted that you didn't read the site thoroughly, and that you now understand how GS works, the nature of the problem, and that the developer had done what he could.
Additionally, you posted your rateitall review with a full understanding of the situation, and yet you still painted yourself in a completely innocent light. And again, it's out of Garrett's hands at the moment -- which you know because you read his blog post -- but your review reads like he's just sitting on his laurel doing nothing but counting his stack of $1.39 checks. (And he replied "after several days?" Looks like one day to me.)
While Garrett perhaps shouldn't have marked it as solved at first (personally I think it was reasonable as I would have read the thread to get more details), this is hardly a trespass worthy of such vitriol. -
The company says
this solves the problem
Loading Profile...



EMPLOYEE