Tom,

In order to see your WIRE, I will need build permissions please.

Tom,

what version of the engine do you have listed in the settings page for your App in the studio? If it isn't on 1.3, I would move it there and this should correct the Atlantic issues.

For PDF quality, it really depends on how image heavy they are, the more images the more layers and the time it takes to load, so size becomes an issue. If you test on a Retina iPad and it looks good when you pinch and zoom in, then you are in good shape. We sometimes say that "print-ready" pdfs are optimal, but really there is such a wide range of acceptable sizes and layers, that it is hard to nail down an exact metric other than make sure your dimensions match that of the screen (1024x768 or 2048x1536)

Tom,

This might go faster if I can see your code. Can you invite me as a collaborator? icahill@rarewire.com

Have you seen this behavior in Ad-Hoc builds or just in Fusebox?

Very interesting. These must be leftover test assets living in the WIRE engine build. We removed a bunch of these when we came out of beta, and must have missed them. I will look into getting these removed.

In the meantime, these are probably showing up because you haven't correctly defined the name of the images you want in your thumbnail menu.

step currently is not associated to an object property, so there isn't a good way to redefine it.

Instead you might consider using variables and conditional logic to define the number of articles returned in your feed directly on your objects.

Awesome, glad it was a quick fix, you guys are really rolling!

Is there a chance you can show me your WIRE, that would be helpful. Without the code, I might suggest that you add wirename="nameofwire.wire" to your load tags, otherwise the system will look for wire updates everytime.

Jake,

Try your builds again. That error is indicative of an error on our end and it should have been corrected. Sorry about that.