On Aug 19, 2012, at 6:22 PM, Paul Ryland wrote:
> Strangely though, it's only become a problem with MfA 4.2.5. I can't say for
> sure that it didn't happen with earlier versions, but now it happens very
> consistently.
Code cleanup and refactoring on our part. ;-)
We used to have 3 different d
Hi Jon,
No, there's no particularly good reason why I'm using busybox, I forget
even why it's there, so I can certainly work around the problem by
uninstalling it. Strangely though, it's only become a problem with MfA
4.2.5. I can't say for sure that it didn't happen with earlier versions,
but now
On Aug 15, 2012, at 8:17 PM, psryland wrote:
> I've been noticing this deployment error a lot with the latest alpha version
> of MfA (v4.2.5, installer: mono-android-4.2.5.195540401.msi). The device I'm
> deploying to has this Busybox version: BusyBox v1.20.2-Stericson (2012-07-04
> 21:33:31 CD
On Aug 15, 2012, at 8:17 PM, psryland wrote:
> I've been noticing this deployment error a lot with the latest alpha version
> of MfA (v4.2.5, installer: mono-android-4.2.5.195540401.msi). The device I'm
> deploying to has this Busybox version: BusyBox v1.20.2-Stericson (2012-07-04
> 21:33:31 CD
Hi,
I've been noticing this deployment error a lot with the latest alpha version
of MfA (v4.2.5, installer: mono-android-4.2.5.195540401.msi). The device I'm
deploying to has this Busybox version:
BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT)
A workaround seems to be to select 'rebuild-al
