Yes, it doesn't expire until this coming December.

On Mon, Jun 9, 2014 at 12:57 PM, OmPrakash Muppirala <bigosma...@gmail.com>
wrote:

> Hmm, do you have a valid and current ios development certificate?  I let
> mine expire and started seeing weird things.  It was a couple of days
> before I realized that it had expired.
>
> Thanks,
> Om
>
>
> On Mon, Jun 9, 2014 at 10:54 AM, Nick Collins <ndcoll...@gmail.com> wrote:
>
> > Not unless IntelliJ is putting it in automatically for me. I don't have
> it
> > set and I don't see it in the console as being one of the compiler
> options
> > specified.
> >
> >
> > On Mon, Jun 9, 2014 at 12:41 PM, OmPrakash Muppirala <
> bigosma...@gmail.com
> > >
> > wrote:
> >
> > > I see this exact behavior when I use the new "-useLegacyAOT no" custom
> > > compiler directive, so I stopped using it.  Any chance that could be
> your
> > > problem?
> > >
> > > Thanks,
> > > Om
> > >
> > >
> > > On Mon, Jun 9, 2014 at 10:36 AM, Nick Collins <ndcoll...@gmail.com>
> > wrote:
> > >
> > > > Hey guys,
> > > >
> > > > I'm posting this here because I'm not sure if this is an AIR SDK
> issue,
> > > and
> > > > issue with the Flex SDK, or an issue perhaps with the way the
> installer
> > > > overlays the two.
> > > >
> > > > This could also potentially be an IDE issue, though I'm not sure.
> > > >
> > > > The setup:
> > > > • App is built using Flex 4.12.1 and AIR 13
> > > > • Developed in IntelliJ IDEA 13
> > > > • 3rd gen Retina iPad connected to MacBook Pro via USB and has the
> > > > appropriate mobile provisioning profile installed
> > > >
> > > > The problem(s):
> > > > 1) even though ADT can list and see the USB, the app fails to install
> > via
> > > > ADT to the connected iPad. No errors displayed in the console, the
> > > > application installation simply fails.
> > > > 2) if I manually install debug app to iPad via iTunes, it installs
> > > without
> > > > error. However, the debugger will still not connect to the app.
> > > > 3) Deployment via ADT does work to the iOS simulator, as does
> > debugging.
> > > > However, even though the application descriptor states it is only
> > > targeting
> > > > iPad devices and not iPhones, the simulator will only ever launch as
> a
> > > 3.5"
> > > > iPhone. Naturally, when I change it to iPad, the app is quit and so
> > > > therefore so does my debugger connection.
> > > >
> > > > Has anyone here experienced these issues before and know if the
> problem
> > > is
> > > > somewhere on our side, or not?
> > > >
> > > > Nick
> > > >
> > >
> >
>

Reply via email to