Betamax can't connect to server error 404

[GoogleCodeExporter]

What steps will reproduce the problem?
1. All the tme
2. Since new web on rynga, actionvoip, ...
3. Error still persistent 

What is the expected output? What do you see instead?
Failed to connect to server error 404

What version of the product are you using? "Last" is not appropriate. Make
sure you tell at least which app you are using. On what operating system?

The latest one
Please provide any additional information below.

Original issue reported on code.google.com by rusty5...@gmail.com on 6 Apr 2012 at 10:33

[GoogleCodeExporter]

Do you use the new connector.
Please be more explicit than "last".

Original comment by f...@ub0r.de on 7 Apr 2012 at 7:32

• Changed state: NeedMoreInfos
• Added labels: Product-Betamax

[GoogleCodeExporter]

Original comment by f...@ub0r.de on 7 Apr 2012 at 7:33

[GoogleCodeExporter]

I use v4.2.8 websms app, and on the betamax connecter can't find what
version it is, but it does not show any update available

-----P�vodn� spr�va-----
Od: websmsdroid@googlecode.com [mailto:websmsdroid@googlecode.com] 
Odoslan�: 07 April 2012 08:33
Komu: rusty5485@gmail.com
Predmet: Re: Issue 691 in websmsdroid: Betamax can't connect to server error
404

Original comment by rusty5...@gmail.com on 7 Apr 2012 at 4:01

[GoogleCodeExporter]

You're either using this
https://play.google.com/store/apps/details?id=de.ub0r.android.websms.connector.b
etamax
or this
https://play.google.com/store/apps/details?id=de.ub0r.android.websms.connector.b
etamax2
connector. I'm the maintainer of the second one, which is based on the first 
one. If you open the Google Play Store you should at least be able to 
distinguish the publisher (Jon Agüera or Thomas Ritter).
So this leaves us with two options
1) If you're using the first connector, uninstall it and install the second one.
2) If you're using the second connector: which provider are you using? There's 
a list of working and non-working providers in the app description.

To further analyze this problem, you could try to open a specific URL in your 
browser. If your provider URL is e.g. "www.myprovider.com", you could try to 
open:
https://www.myprovider.com/myaccount/getbalance.php
(change www.myprovider.com accordingly)
If this URL returns a white page with a single "0"-digit, then your provider 
should work theoretically. If you are forwarded to a HTTP 404 error page, then 
the connector is not compatible with your provider.

Original comment by ritter.t...@gmail.com on 8 Apr 2012 at 11:02

[GoogleCodeExporter]

I am using the first one as it was working for a long time, just stopped
after the provider web update.
I also tried yours, but it does not work either as my provider is on NON
working list (Rynga and Actionvoip).
So the program is useless for me, and I paid for it as well. Can I get
refund as I won't be able to use it anymore?

-----P�vodn� spr�va-----
Od: websmsdroid@googlecode.com [mailto:websmsdroid@googlecode.com] 
Odoslan�: 08 April 2012 12:03
Komu: rusty5485@gmail.com
Predmet: Re: Issue 691 in websmsdroid: Betamax can't connect to server error
404

Original comment by rusty5...@gmail.com on 8 Apr 2012 at 8:18

[GoogleCodeExporter]

i guess we have to wait for a fix from jon, the old maintainer.

i'm sad to say, that refund is not possible, as the google checkout account 
gives me no possibility to do it.

Original comment by f...@ub0r.de on 9 Apr 2012 at 10:13

[GoogleCodeExporter]

just to clarify: the old connector does use the same mechanism to send messages 
and to check the balance. I have only rewritten some internals. I have received 
one other bug report via email and the person told me that my connector used to 
work, but stopped about 2-4 weeks ago. It seems that some Betamax clones have 
disabled or changed the mechanism to send messages. The problem is: this is 
poorly documented and it used to work for a few years now. I will look into 
this but cannot promise any solution, as I'm not affiliated to these providers, 
I'm merely doing this in my spare time.

Original comment by ritter.t...@gmail.com on 9 Apr 2012 at 11:12

[GoogleCodeExporter]

I have the same problem.
It seems that getbalance.php stops working in many betamax providers, and
there are no support from providers on how to obtain balance again.

I think that the best option is to remove this connector from market,
because it's difficult to mantain and can cause many complains to Felix.

What do you think?

Original comment by jonagu...@gmail.com on 10 Apr 2012 at 5:15

[GoogleCodeExporter]

Good to hear from you personally, Jon. I guess Felix has to answer this, but I 
don't really see the problem. In the app description, I have listed the 
providers that should work and those that will probably not. In addition, I 
have written a shell script that generates balance URLs and checks HTTP status 
codes. Now, that some of those providers stopped working a few weeks ago is 
unfortunate, but half of those I know of still do. The only reason that I see 
to pull the app is because we get too many complaints, but I have received two 
so far. What are your thoughts?

Original comment by ritter.t...@gmail.com on 10 Apr 2012 at 5:59

[GoogleCodeExporter]

i think, there is no need to have two connectors on the market.
but removing both is not necessary at the moment.

i know, that not working connectors may lead to bad stats in market for the 
main app. but i can live with that problem ;)

Original comment by f...@ub0r.de on 10 Apr 2012 at 7:14

[GoogleCodeExporter]

Ok. Then I'm going to pull my app. In addition, last month there are
reports that it's not working on ICS, so...

Thanks for your help and your patiente with my first java code.

See you...
El 10/04/2012 21:14, <websmsdroid@googlecode.com> escribió:

Original comment by jonagu...@gmail.com on 10 Apr 2012 at 7:31

[GoogleCodeExporter]

just FYI, I changed the script to call both the balance URL and the message URL 
(first and second HTTP response) and to my surprise, most providers only offer 
the latter (see attachment). Is there a possibility to deactivate balance 
checks at runtime?

Original comment by ritter.t...@gmail.com on 10 Apr 2012 at 8:59

Attachments:

• providers_2012-04-10.txt

[GoogleCodeExporter]

@jon: thank you very much for your time. and please don't hesitate to share a 
few lines of code with us :)

@thomas: UPDATE is one of the capabilities which could be disabled, but it 
would only work on connector's init. but you could replace the doUpdate() call 
with something sane. setBalance("?") or something.

Original comment by f...@ub0r.de on 11 Apr 2012 at 5:25

• Added labels: Component-Persistence

[GoogleCodeExporter]

There is a new Betamax Connector version available, which should fix the 404 
errors and fix problems with sending messages. 
https://play.google.com/store/apps/details?id=de.ub0r.android.websms.connector.b
etamax2

Original comment by ritter.t...@gmail.com on 12 May 2012 at 12:45

[GoogleCodeExporter]

Original comment by f...@ub0r.de on 17 Jun 2012 at 2:48

• Changed state: Fixed