Error on failure dialog

[Pent]

Hello, just test driving.

It appears that after the library has decided the app is unlicenced
and is showing the block dialog (with 'purchase' or 'exit'), the
dialog can be exited with the search key.

The callback then also doesn't take place.

You might want to look at the camera button too (in fact any
unexpected KeyEvent).

This on an N1 running 2.2.

You also have a spelling error in the developer nag screen :)

It would be nice if you could catch the host-not-found exception that
fills the log if there's no connectivity too.

Finally: how reliable is the server you use to confirm the developer
key (in terms of uptime) ?

Thanks,

Pent

[Pent]

p.s. my big concern about this library is the two account/credentials
permissions combined with the closed source. Predictably, I guess :)

Pent

[Pent]

Now I think about it, why not package it as a separate app and put it
on the market for free.

That removes two problems:

- closed source/ permissions
- developers no longer have to deal with updating the library

And the user could then delete AAL once the licence is confirmed.

The API might be slightly more complicated, probably via ordered
broadcasts.

Pent

[David Keyes]

Thanks for the feedback.  Fixed the spelling error, and looking at the other issues...

[David Keyes]

I considered this, but wasn't sure how to do things in a way that wouldn't be incredibly easy to spoof.  I assume you're suggesting something like what I was thinking:

MyApp             AALBroadcastReceiver

  |
  X--- validateMyAppIntent --> X

  X <-- validationSuccessfullMsg --
  |
 

But it seems like it would be incredibly easy for others to register listeners for the same intents, and return messages that say "registered".  Can't see how I do it without proprietary code in the app.

Also, I've been resisting open sourcing because of the reduction in barriers to would-be pirates.

Dave

[Pent]

I was thinking more of a startActivity/result code. You can verify the
calling package from your activity.

In any case, I went for a custom solution currently since it gives me
some protection for:

- pre eclair devices
- outside-the-market sales

If AAL could get past the closed source/scary permissions model I'd
certainly consider buying a licence though.

I wish you luck!

Pent

On Jun 3, 10:06 pm, David Keyes <keyes...@gmail.com> wrote:
> I considered this, but wasn't sure how to do things in a way that wouldn't
> be incredibly easy to spoof.  I assume you're suggesting something like what
> I was thinking:
>
> MyApp             AALBroadcastReceiver
>
>   |
>   X--- validateMyAppIntent --> X
>
>   X <-- validationSuccessfullMsg --
>   |
>
> But it seems like it would be incredibly easy for others to register
> listeners for the same intents, and return messages that say "registered".
> Can't see how I do it without proprietary code in the app.
>
> Also, I've been resisting open sourcing because of the reduction in barriers
> to would-be pirates.
>
> Dave
>