We cache the local certificates but we ask the wrong questions and some
things might not work with that flow.
We streamlined that in the new flow and will try to reuse the local
certificate without even asking. You could still run the wizard to generate
provisioning and push certificates only.
There's also a systemic problem if you have multiple projects, you tend to
be prompted to create
new certificates which invalidates all the other certificates. There
ought to be a concept of a
single pair of certificates shared by all projects.
--
You received this message because you are
We're currently reworking the flow/interaction of the certificate wizard
from the ground up. I agree it's pretty complicated and error prone.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop
I succeeded in making new builds after re-running the certificate wizard
and
answering "yes" to all the "generate new" and "override existing" questions.
IMO something is broken if I can run through a lengthy interaction with the
certificate wizard, have no apparent errors, and still generate
On Friday, June 26, 2020 at 12:00:03 AM UTC-7, Dave Dyer wrote:
>
> All the certificates and links to them in the preferences file
> seem to be correct, and all the certificates have today's date.
>
>
--
You received this message because you are subscribed to the Google Groups
"CodenameOne
All the certificates and links to them in the preferences file
seem to be correct, and all the certificates have today's date.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails
I think I had manually relocated the old certs to a place in my dev source
tree, but
I didn’t redo the relocation after making new certs. I left everything
exact as the
Wizard created it.
On Thursday, June 25, 2020 at 7:50:59 PM UTC-7, Shai Almog wrote:
>
> It seems your certificate is missing
Expired, but I ran through the certificate wizard successfully.
On Thursday, June 25, 2020 at 7:50:59 PM UTC-7, Shai Almog wrote:
>
> It seems your certificate is missing from the build. Did something change
> in your paths?
> Did your certificate expire?
>
--
You received this message
It seems your certificate is missing from the build. Did something change
in your paths?
Did your certificate expire?
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it,
It's priorities. This is a problem that exists in one outlier case to one
developer.
If you look thru our open issues you will see that there alone we have a
lot of things to fix that are crucial to everyone.
There are also quite a lot of tasks for enterprise developers that aren't
public but
Sometimes when you're looking for a problem you have to do something you
don't
intend to be permanant. If you could do it only for my account, I'd gladly
take
the performance hit while we collect data.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne
I am talking about the logs and not the builds. They are huge.
One of the reasons we don't return them by default is that they will slow
the build process for everyone.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe
If you kept the logs but not the builds, you'd have a lot more headroom.
Also, it would be useful (in this case) if the "save sources" went ahead
even if the build failed.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To
If they were long enough we would run out of storage space, there is some
information but it's not immediately available.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from
Assuming you have multiple servers, is there any information that would
identify
which one was used in this particular case? An obvious piece of
information to
look for would be if the failed builds were all on the same server.
--
You received this message because you are subscribed to the
I assume you're referring to some other log than the one I have access to.
You ought to keep your logs long enough for them to be useful, but in this
case I assume
the most useful information would be to retrieve the culprit
com_codename1_ui_Component.m
which would be long gone.
--
You
You need to keep your logs long enough for them to be useful.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Unfortunately I can't see this in the logs by the time I see these messages.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
There's no way to reproduce it from here. These build failures come in
clusters; repeating the
exact same build seems to eventually succeed. My working hypothesis is
that there's a
resource exhaustion problem, which is resolved when the server gets spun
down and replaced.
--
You received
I'll need some way to reproduce this...
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to codenameone-discussions+unsubscr...@googlegroups.com.
Visit
20 matches
Mail list logo
