Error: Template not Found. Older Build: 2014.2223

Solar2D Daily Builds and Public Releases
#1

Hi Corona;

I am trying to make an Android build for the Nook and I am using older build 2014.2223 because it supports Android 2.2 (and this is also a an old build which is post Graphics 2.0 – which is good).

This is super important for us to be able to do as we have large installed bases of our apps (Just 2 Words, Just Jumble) on the original Nook Color devices – which B&N continues to sell. And those devices need 2.2.

Here is message I get when trying to publish my APK on my PC:

A device build error occurred on the server.

BuildID: 54b158aa767d2
Error: Template not found.

Build Number: 2014.2223
Platform: android-nook
Platform Version: 2.2
Template Type: basic

I was able to make APKs of my apps with this Corona build successfully last Fall. Any idea what is going on?

Thanks;

Steve Bullock

#2

I can confirm that I also got this error tonight. I was using build number 2014.2263 though.

#3

Hi Richards App Store;

I was reading through another thread and saw this post from just a few days ago where Joshua (of Corona) said:

QUOTE:

And for your information, the 1st gen Kindle Fire is an Android 2.3.3 device, which is the minimum version that Corona supports.  In my opinion, it’s still important for us to support the 1st gen Kindle Fire.  I was a big proponent to keep Nook Color (Android 2.2) support here as well until Google’s newest features (which were in high demand) made it extremely difficult for us to continue 2.2 support.  But if it makes you feel any better, we do go out of our way to maintain support for older versions of Android as long as possible since the Android OS version fragmentation issue is painfully real. (said on January 5th)

UNQUOTE

So I am hoping that someone at Corona can shed some light on this so that I can use the older build to make a Nook version. I tested again this morning and get the same error message as I did on Friday (quoted above).

Thanks;

Steve

#4

Hey sbullock,

That’s good to hear. I’ve heard Corona Staff say before that they do not provide support for older builds generally, but I don’t imagine that excludes when an older build just simply becomes unbuildable. Since it happened to 2263 and 2223 I Imagine it’s pretty widespread across a lot of older builds and hopefully something just needs to get reuploaded on Corona’s end. From the error saying “Template not found” I’m guessing that whatever file/instructions stored on the build servers for these specific builds just got deleted or moved or something but that’s just a total guess. With majority of what’s left of the NOOK market being the NOOK Color I am hopeful that this will be fixed. Also I did too test it this morning and had the same error so it is not working as of yet. I submitted a bug report about it.

Tyler

#5

Hi Richard;

Thanks for the info. I think I’d better submit a bug report too. Still throwing the same error when trying to build today (1/13).

Steve

#6

Hi Tyler, Steve,

I’m not sure how this constitutues a “bug”. The minimum version of Android is now 2.3.3 as Joshua quoted. If you’re using an older build but (possibly) a plugin that requires 2.3.3 then there will be build issues. What plugins are you using, if any?

Take care,

Brent

#7

Hey Brent,

The issue is we’ve been using somewhat older builds to be able to build for NOOK Color and now suddenly when we go to build we get an error thrown back form the build servers saying template not found. I made a build 12/29/2014 and it had no issues building using version 2014.2263. Now in the last few days, without any significant changes (literally all that I had changed was I added some additional elements to a table in my code) and without getting any errors in the app itself, we are getting this template not found error when building. This is the error that is popping up now when building:

  owlyVJs.png

I am not using any plugins at all. So something within a matter of 10-12 days changed on the build server is what it acts like that is preventing builds of this version from being built possibly? Just my guess.

Thanks for your help,

Tyler

Edit: I went and made a new project that is essentially empty, just a main.lua that runs in the simulator and that’s it, to make sure no plugins were being used. And I still get the same build error.

#8

Hello again,

If you didn’t see it already, just for reference, here is our announcement on dropping support for 2.2, from way back last April.

http://coronalabs.com/blog/2014/04/16/changes-in-minimum-os-version-android-2-3-3/

In any case, we’re checking out the reason why this error is occurring. However, remember that you’re going to be limited to building with older versions for other reasons as well. For example, Mac users who have upgraded to OS X 10.9.5 won’t be able to run the older Corona Simulators (e.g. #2263) because Apple changed the code signing requirements. In addition, by using an old build, you’ll face other issues and bugs that have since been fixed, so clearly, do this at your own risk (I’m sure you’re fully aware of this, but I just want to emphasize it).

Best regards,

Brent

#9

Hey Brent,

Yeah that’s fully understood. I wouldn’t expect any support for a build that old outside of in this case the fact that it just literally won’t let a build go through. I’m on a Windows 7 Machine, I had to use Windows instead of Mac because of that Mac issue you’re referring to. It’s clearly though not a bug with code or anything that I can think of on my end seeing as how it was working fine just a week and a half ago and without any real change has just stopped building.

Thanks for your help it is much appreciated,

Tyler

#10

Brent,

Just wanted to check if there is any update. We’re unable to build for NOOK Color with this error so the update I was about to publish is dead in the water.

Thanks,
Tyler

#11

Hi Tyler,

We are still looking into this, but unfortunately we can’t prioritize it (for the reasons I mentioned). Perhaps next week we’ll locate the issue.

Thanks,

Brent

#12

Hi Brent;

Anything you can do on this would be greatly appreciated. I went back and read your announcements about not supporting 2.2 moving forward. But a wonderful thing about Corona (and one of the reasons I love it) is that you have studiously avoided withdrawing the ability of developers to use OLDER BUILDS (and the announcement said nothing concerning that).

I’m guessing that there were “Templates” on your server as late as November (and removed/moved/changed since) for making these builds that inadvertently aren’t where they should be. Of course that is just a guess. :slight_smile:

The Just Jumble app we are hoping to continue updating was B&N’s featured Free App Friday download over the Thanksgiving weekend this past November and it picked up about 17,000 downloads/installs on top of a good sized user base already in place. The stats on these folks are about 40% Nook Color (2.2) and I sure hate the idea that we’d never be able to update them. BTW, the only plugin we use is Fortumo for in-app purchasing.

Thanks for any light you can shed on this change on your servers.

Steve

#13

Hi,

This happened to me right now.

build number: 2014.2263

I’m hoping to support platform 2.2 just for the Nook Color.

Any advise from Corona ??

Thank you,

Bobby

#14

Hi Corona,

I have quite a following in B&N using Nook Color, and

It will be really bad to stop supporting that user base.

I hope Corona can put the template back in their server for Android 2.2

Just to build for the Nook Color.

Build number i utilize:   2014.2263, just to create the 2.2 APK.

Thank you,

-Bobby

#15

The engineers that work on the build servers  are on a higher priority project at the moment.   We know this is important to you and will get to it as soon as we get the time for them to work on it.

Rob

#16

Is there a way to tell the manifest, that  the app is compatible with platform 2.2 ? even if it was compiled for 2.3 ?

The reason I’m asking this, is because I’m able to install the app to Nook color with platform 2.3.3 through an ADB install.

#17

No.  It’s not just the manifest, it would actually need to support Android 2.2 to work.

Rob

#18

Ok Thanks Rob, I’ll just wait for this issue to be fixed. I hope soon, my Nook color users are waiting for my app update.

#19

Hi Rob,

Any news regarding this issue ?

Thank you,

-Bobby

#20

It’s on our list to fix, but it may be a few more weeks before we get to it.

Rob