I'm not sure what the offical plans are but it looks like igal's repo
has not been updated since last year. So if any android dev's out
there want to pick up the project:
> I'm not sure what the offical plans are but it looks like igal's repo
> has not been updated since last year. So if any android dev's out
> there want to pick up the project:
>> I'm not sure what the offical plans are but it looks like igal's repo
>> has not been updated since last year. So if any android dev's out
>> there want to pick up the project:
>> I'm not sure what the offical plans are but it looks like igal's repo
>> has not been updated since last year. So if any android dev's out
>> there want to pick up the project:
It built fine for me, and is showing this years schedule. I have an
Android Market publisher account should I put it up? It would show up
as a new app rather than an update because I'm a different publisher.
I think we should let Igal have a chance to update the app already in the
market. Less chance of confusing people.
On Jun 25, 2012 3:30 PM, "Daniel Johnson" <tekno...@gmail.com> wrote:
> It built fine for me, and is showing this years schedule. I have an
> Android Market publisher account should I put it up? It would show up
> as a new app rather than an update because I'm a different publisher.
On Mon, Jun 25, 2012 at 3:32 PM, Jacob Helwig <ja...@technosorcery.net>wrote:
> I think we should let Igal have a chance to update the app already in the
> market. Less chance of confusing people.
Thanks for noticing that the Android app was out of date, Scott. I
appreciate the pull requests from Jacob and Don. I'm reviewing these and
will make any other necessary changes to switch it to 2012. I should have
it published by the evening and will email when done.
I second that we should give igal a chance to take charge. Also I
noticed that the Readme had a 2011 and the project desc is also
2011'd.
On Mon, Jun 25, 2012 at 3:32 PM, Jacob Helwig <ja...@technosorcery.net> wrote:
> I think we should let Igal have a chance to update the app already in the
> market. Less chance of confusing people.
> On Jun 25, 2012 3:30 PM, "Daniel Johnson" <tekno...@gmail.com> wrote:
>> It built fine for me, and is showing this years schedule. I have an
>> Android Market publisher account should I put it up? It would show up
>> as a new app rather than an update because I'm a different publisher.
I didn't see your reply before I chimed in again. It's great to have
you back in town, let us know if there's anything we can do to help...
other wise we'll see you tomorrow =)
On Mon, Jun 25, 2012 at 3:38 PM, Igal Koshevoy <i...@pragmaticraft.com> wrote:
> On Mon, Jun 25, 2012 at 3:32 PM, Jacob Helwig <ja...@technosorcery.net>
> wrote:
>> I think we should let Igal have a chance to update the app already in the
>> market. Less chance of confusing people.
> Thanks for noticing that the Android app was out of date, Scott. I
> appreciate the pull requests from Jacob and Don. I'm reviewing these and
> will make any other necessary changes to switch it to 2012. I should have it
> published by the evening and will email when done.
On Mon, Jun 25, 2012 at 3:42 PM, benh <ben.hen...@gmail.com> wrote:
> I didn't see your reply before I chimed in again. It's great to have
> you back in town, let us know if there's anything we can do to help...
> other wise we'll see you tomorrow =)
Thanks for the pull request and kind words, Ben.
I finally have Eclipse up and running the app again, so I'm hoping that
finishing this off will be pretty straightforward. If not, I'll ask for
help.
On Mon, Jun 25, 2012 at 3:48 PM, Igal Koshevoy <i...@pragmaticraft.com>wrote:
> On Mon, Jun 25, 2012 at 3:42 PM, benh <ben.hen...@gmail.com> wrote:
>> I didn't see your reply before I chimed in again. It's great to have
>> you back in town, let us know if there's anything we can do to help...
>> other wise we'll see you tomorrow =)
> Thanks for the pull request and kind words, Ben.
> I finally have Eclipse up and running the app again, so I'm hoping that
> finishing this off will be pretty straightforward. If not, I'll ask for
> help.
PS: I'll add Ben to the app's contributors list. :)
If you really want to I'm not going to complain but really all I did
was notice that the readme hadn't been updated... you have the power
I'll leave it to you.
On Mon, Jun 25, 2012 at 3:49 PM, Igal Koshevoy <i...@pragmaticraft.com> wrote:
> On Mon, Jun 25, 2012 at 3:48 PM, Igal Koshevoy <i...@pragmaticraft.com>
> wrote:
>> On Mon, Jun 25, 2012 at 3:42 PM, benh <ben.hen...@gmail.com> wrote:
>>> I didn't see your reply before I chimed in again. It's great to have
>>> you back in town, let us know if there's anything we can do to help...
>>> other wise we'll see you tomorrow =)
>> Thanks for the pull request and kind words, Ben.
>> I finally have Eclipse up and running the app again, so I'm hoping that
>> finishing this off will be pretty straightforward. If not, I'll ask for
>> help.
> PS: I'll add Ben to the app's contributors list. :)
So I'm ready to publish the updated app, but can't.
The problem is I can't get into the Google Play account associated with the
app. No matter what account I log into, it insists that I don't have a
profile and need to create a new one. However, I don't want to do that
because that'd create another copy of the app rather than update the
existing one, and I'd have to create a new profile with a new name that's
not my own name.
On Mon, Jun 25, 2012 at 4:41 PM, Igal Koshevoy <i...@pragmaticraft.com>wrote:
> Help.
> So I'm ready to publish the updated app, but can't.
> The problem is I can't get into the Google Play account associated with
> the app. No matter what account I log into, it insists that I don't have a
> profile and need to create a new one. However, I don't want to do that
> because that'd create another copy of the app rather than update the
> existing one, and I'd have to create a new profile with a new name that's
> not my own name.
> Ideas?
I couldn't find anything online to help me resolve this, so I put in a
ticket for Google on this issue.
How long should I wait to hear back from Google before giving up and
registering a new account and publishing a new app? I'm thinking of
publishing the new version of the app with a "2012" appended to it so it's
possible to distinguish it from the previous one. Sigh.
I've had issues with the developer side of the play market and multiple
Google accounts. Unfortunately the only suggestion I have is to make sure
you're completely logged out and keep trying different accounts. It's
pretty lame.
On Jun 25, 2012 5:33 PM, "Igal Koshevoy" <i...@pragmaticraft.com> wrote:
> On Mon, Jun 25, 2012 at 4:41 PM, Igal Koshevoy <i...@pragmaticraft.com>wrote:
>> Help.
>> So I'm ready to publish the updated app, but can't.
>> The problem is I can't get into the Google Play account associated with
>> the app. No matter what account I log into, it insists that I don't have a
>> profile and need to create a new one. However, I don't want to do that
>> because that'd create another copy of the app rather than update the
>> existing one, and I'd have to create a new profile with a new name that's
>> not my own name.
>> Ideas?
> I couldn't find anything online to help me resolve this, so I put in a
> ticket for Google on this issue.
> How long should I wait to hear back from Google before giving up and
> registering a new account and publishing a new app? I'm thinking of
> publishing the new version of the app with a "2012" appended to it so it's
> possible to distinguish it from the previous one. Sigh.
On Mon, Jun 25, 2012 at 6:06 PM, Jacob Helwig <ja...@technosorcery.net> wrote:
> I've had issues with the developer side of the play market and multiple
> Google accounts. Unfortunately the only suggestion I have is to make sure
> you're completely logged out and keep trying different accounts. It's pretty
> lame.
> On Jun 25, 2012 5:33 PM, "Igal Koshevoy" <i...@pragmaticraft.com> wrote:
>> On Mon, Jun 25, 2012 at 4:41 PM, Igal Koshevoy <i...@pragmaticraft.com>
>> wrote:
>>> Help.
>>> So I'm ready to publish the updated app, but can't.
>>> The problem is I can't get into the Google Play account associated with
>>> the app. No matter what account I log into, it insists that I don't have a
>>> profile and need to create a new one. However, I don't want to do that
>>> because that'd create another copy of the app rather than update the
>>> existing one, and I'd have to create a new profile with a new name that's
>>> not my own name.
>>> Ideas?
>> I couldn't find anything online to help me resolve this, so I put in a
>> ticket for Google on this issue.
>> How long should I wait to hear back from Google before giving up and
>> registering a new account and publishing a new app? I'm thinking of
>> publishing the new version of the app with a "2012" appended to it so it's
>> possible to distinguish it from the previous one. Sigh.
On Mon, Jun 25, 2012 at 6:06 PM, Jacob Helwig <ja...@technosorcery.net>wrote:
> I've had issues with the developer side of the play market and multiple
> Google accounts. Unfortunately the only suggestion I have is to make sure
> you're completely logged out and keep trying different accounts. It's
> pretty lame.
Thanks. Tried that with eight different accounts, but nada.
I even found my email receipt for the Android developer registration, but
clicking the details link gives me an "access denied" error despite trying
to view it from the same account that the receipt was mailed to. None of my
other accounts can view it either.
So either I registered the account using a Google account that I
haven't thought to try, or something broke during the various Google
account changes and transition from Marketplace to Play during the last
year.
On Mon, Jun 25, 2012 at 6:59 PM, Igal Koshevoy <i...@pragmaticraft.com> wrote:
> On Mon, Jun 25, 2012 at 6:06 PM, Jacob Helwig <ja...@technosorcery.net>
> wrote:
>> I've had issues with the developer side of the play market and multiple
>> Google accounts. Unfortunately the only suggestion I have is to make sure
>> you're completely logged out and keep trying different accounts. It's pretty
>> lame.
> Thanks. Tried that with eight different accounts, but nada.
> I even found my email receipt for the Android developer registration, but
> clicking the details link gives me an "access denied" error despite trying
> to view it from the same account that the receipt was mailed to. None of my
> other accounts can view it either.
> So either I registered the account using a Google account that I
> haven't thought to try, or something broke during the various Google account
> changes and transition from Marketplace to Play during the last year.
> Is this something that we can just have for side loading? Seems we
> could just post the apk on the wiki or something?
> On Mon, Jun 25, 2012 at 6:59 PM, Igal Koshevoy <i...@pragmaticraft.com> wrote:
>> On Mon, Jun 25, 2012 at 6:06 PM, Jacob Helwig <ja...@technosorcery.net>
>> wrote:
>>> I've had issues with the developer side of the play market and multiple
>>> Google accounts. Unfortunately the only suggestion I have is to make sure
>>> you're completely logged out and keep trying different accounts. It's pretty
>>> lame.
>> Thanks. Tried that with eight different accounts, but nada.
>> I even found my email receipt for the Android developer registration, but
>> clicking the details link gives me an "access denied" error despite trying
>> to view it from the same account that the receipt was mailed to. None of my
>> other accounts can view it either.
>> So either I registered the account using a Google account that I
>> haven't thought to try, or something broke during the various Google account
>> changes and transition from Marketplace to Play during the last year.
On Mon, Jun 25, 2012 at 8:49 PM, Jacob Helwig <ja...@technosorcery.net> wrote:
> Sure, but IIRC there are still providers that prevent that from working on "their" phones.
> On Jun 25, 2012, at 8:45 PM, benh wrote:
>> Is this something that we can just have for side loading? Seems we
>> could just post the apk on the wiki or something?
>> On Mon, Jun 25, 2012 at 6:59 PM, Igal Koshevoy <i...@pragmaticraft.com> wrote:
>>> On Mon, Jun 25, 2012 at 6:06 PM, Jacob Helwig <ja...@technosorcery.net>
>>> wrote:
>>>> I've had issues with the developer side of the play market and multiple
>>>> Google accounts. Unfortunately the only suggestion I have is to make sure
>>>> you're completely logged out and keep trying different accounts. It's pretty
>>>> lame.
>>> Thanks. Tried that with eight different accounts, but nada.
>>> I even found my email receipt for the Android developer registration, but
>>> clicking the details link gives me an "access denied" error despite trying
>>> to view it from the same account that the receipt was mailed to. None of my
>>> other accounts can view it either.
>>> So either I registered the account using a Google account that I
>>> haven't thought to try, or something broke during the various Google account
>>> changes and transition from Marketplace to Play during the last year.
On Mon, Jun 25, 2012 at 8:56 PM, benh <ben.hen...@gmail.com> wrote:
> ~le sigh~ why is this whole "lets keep the world safe for gramma"
> mentality making life difficult
It does, but there's almost always something sinister behind it. In this
case, the flimsy rationalization of security is a cheap ploy to force
people to use the store.
On Mon, Jun 25, 2012 at 8:45 PM, benh <ben.hen...@gmail.com> wrote:
> Is this something that we can just have for side loading? Seems we
> could just post the apk on the wiki or something?
The options I see are:
1. "side-loading" using a debug key (this is how I tested the apk on
my phone). One downside is phones with the 2011 app will deny the
debug version as they key is different but the java package name is
the same. Also a (small) downside is the marketplace application will
not manage the app. If/when the "real" app is updated, the debug-key
app has to be uninstalled first.
2. Using someone else's Google play account. To do this the java
package name has to change. Adding 2012 to the app title would be a
good idea. A marketplace search would bring up both apps but it should
be clear which is the correct one.
the following chart shows what happens during the 2012 install, and
the 2013 install (assuming Igal's login is recovered by then) using
both options. Each option is listed twice for having and not having
the 2011 app installed first.
2011 2012 2013
sideload installed Uninstall first Uninstall first
sideload not installed OK Uninstall first
market2 installed OK Two apps
market2 not installed OK Two apps
I'd go with the sideload even though its more of a pain it avoids have
two os bridge apps on people's phones and my feeling is Igal's login
will be recovered at some point.
Don Park <don.p...@gmail.com> wrote:
>On Mon, Jun 25, 2012 at 8:45 PM, benh <ben.hen...@gmail.com> wrote:
>> Is this something that we can just have for side loading? Seems we
>> could just post the apk on the wiki or something?
>The options I see are:
>1. "side-loading" using a debug key (this is how I tested the apk on
>my phone). One downside is phones with the 2011 app will deny the
>debug version as they key is different but the java package name is
>the same. Also a (small) downside is the marketplace application will
>not manage the app. If/when the "real" app is updated, the debug-key
>app has to be uninstalled first.
>2. Using someone else's Google play account. To do this the java
>package name has to change. Adding 2012 to the app title would be a
>good idea. A marketplace search would bring up both apps but it should
>be clear which is the correct one.
>the following chart shows what happens during the 2012 install, and
>the 2013 install (assuming Igal's login is recovered by then) using
>both options. Each option is listed twice for having and not having
>the 2011 app installed first.
> 2011 2012 2013
>sideload installed Uninstall first Uninstall first
>sideload not installed OK Uninstall first
>market2 installed OK Two apps
>market2 not installed OK Two apps
>I'd go with the sideload even though its more of a pain it avoids have
>two os bridge apps on people's phones and my feeling is Igal's login
>will be recovered at some point.
>Don
-- Sent from Kaiten Mail. Please excuse my brevity.
On Mon, Jun 25, 2012 at 9:26 PM, Don Park <don.p...@gmail.com> wrote:
> On Mon, Jun 25, 2012 at 8:45 PM, benh <ben.hen...@gmail.com> wrote:
> > Is this something that we can just have for side loading? Seems we
> > could just post the apk on the wiki or something?
> The options I see are:
> 1. "side-loading" using a debug key (this is how I tested the apk on
> my phone). One downside is phones with the 2011 app will deny the
> debug version as they key is different but the java package name is
> the same. Also a (small) downside is the marketplace application will
> not manage the app. If/when the "real" app is updated, the debug-key
> app has to be uninstalled first.
> 2. Using someone else's Google play account. To do this the java
> package name has to change. Adding 2012 to the app title would be a
> good idea. A marketplace search would bring up both apps but it should
> be clear which is the correct one.
> the following chart shows what happens during the 2012 install, and
> the 2013 install (assuming Igal's login is recovered by then) using
> both options. Each option is listed twice for having and not having
> the 2011 app installed first.
> 2011 2012 2013
> sideload installed Uninstall first Uninstall first
> sideload not installed OK Uninstall first
> market2 installed OK Two apps
> market2 not installed OK Two apps
> I'd go with the sideload even though its more of a pain it avoids have
> two os bridge apps on people's phones and my feeling is Igal's login
> will be recovered at some point
Thanks for the details, Don.
Given that I haven't heard anything back from Google and expect this to
take multiple rounds of interactions to resolve correctly, so it's
unreasonable to expect this to be done before much of the conference is
over.
Making the app easy to download is a priority, so side-loading isn't an
option. I'm in the process of setting up a Google Play account for Open
Source Bridge and will publish a "2012" app through it, so it's more
obvious that it's the current version.
