y choice."*
> Yes, it is your choice. And if you can't control your temper and be
> respectful and patient on here, then you have my full support in that
> choice.
>
> Thanks,
> Justin
>
> On Wed, May 13, 2015 at 1:59 PM Ristar >
> wrote:
>
>> Eve
Everyone works within time constraints. Do not assume that I have unlimited
time to wait.
I have already done my due diligence. As it is, there were no helpful links
and no one here helped, and you can get off your high horse because you did
nothing but derail the damn thread.
Your link is pat
you should happen to solve the problem
> yourself then you will post the solution for the benefit of others, but
> apparently you didn't know that either.
>
> On Wed, May 13, 2015 at 9:54 AM, Ristar >
> wrote:
>
>> If no one can answer, the normal assumption would
ally I would
> suggest at least waiting 2 days. And when you do, a very simple question
> like "Has anyone seen anything like this before?" should suffice.
>
> *"I do not appreciate your derailing of the thread."*
> Likewise, I do not appreciate your rudeness. C'
If you are such a fragile and sensitive being, I suggest that you stop
reading. In fact, I would go one step further and suggest that you stop
surfing the web in case it offends your delicate sensibilities. I do not
appreciate your derailing of the thread.
As I have mentioned earlier the same q
On Wednesday, May 13, 2015 at 5:42:16 AM UTC+8, Lew wrote:
>
> Not with rudeness like that, we can't. Yeesh.
>
> On Tuesday, May 12, 2015 at 8:19:02 AM UTC-7, Ristar wrote:
>>
>> Can anyone answer how to fix this? Like, come on, I already showed you
>> the
Can anyone answer how to fix this? Like, come on, I already showed you the
error code. Or is everyone clueless?
On Tuesday, May 12, 2015 at 3:32:12 PM UTC+8, Ristar wrote:
>
> Error:Execution failed for task ':app:dexDebug'.
> > com.android.ide.common.pr
Error:Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException:
org.gradle.process.internal.ExecException: Process 'command 'C:\Program
Files\Java\jdk1.7.0_72\bin\java.exe'' finished with non-zero exit value 3
How to fix this?
--
You received this message be
As written in the title, the Android Studio needs a "*create library*"
function very very very very very badly.
Chucking the source files from everywhere to everywhere else is very bad.
It is the lazy man's way out, yes. But if one uses his own libraries across
many projects, it'd be a nightmar
your hands,
unfortunately.
i didnt try to use the emulator at any point in time coz the emulator is
super slow, needs to boot up, etc. it's much, MUCH faster to just install
the app on the phone and run right away.
On Monday, September 17, 2012 11:51:54 AM UTC+8, janvi wrote:
>
> Hello Ristar
it's fine now...
i guess it takes a few hours for Google to update whatever it needs to
update.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from t
i have set the correct Developer public key in the source code, made the
apk, signed it and uploaded it to Google, and installed it to my phone.
but my phone keeps returning the message "Application error:3".
wat should i do?
--
You received this message because you are subscribed to the Googl
so... i have finished an app and would like to publish, but all of a
sudden, i spotted this Google Licensing API and thought that it would be
pretty cool to incorporate it into the code.
anyway, in the sample code Google put in... there's this String
[CODE]
private static final String BASE64_PU
13 matches
Mail list logo
