Q: Where is Default.png set?

You define in the Project Inspector's "Preview Image" setting:

https://help.apple.com/iadproducer/mac/4.1/help/#iaded90c2711

Documentation about multiple asset versions or renditions:

https://help.apple.com/iadproducer/mac/4.1/help/#iade7b50add

It may be that the project is getting confused about the image renditions because you added them separately. I'd remove the image assets from the Assets sidebar, save the project, add the two images in a single import, then drag the image from the Assets sidebar to the Project Inspector.

Hi,

Can you take a look at the original source files in the Finder? Compare the file size between 1x and 2x.  Is the 1x file larger than the 2x?  If so, try optimizing the 1x file so that the size is smaller than the 2x.  When yo accomplish that, import them again and see if the warning still persists.

-Takayasu

I think rtakayasu is refering to the -file- size, i.e. "bytes on disk", not image size.

What happens if you only import the @2x image?

Yes, sorry about the cofusion, I meant the amount of space on the disk that the file occupies, and not the dimension of the image.

iAd Producer has this import logic where it will use the smaller (in file size) of the two for the low resolution.  So in your original case, the high resolution was the smaller fo the two, so it used it for your low resolution which failed the validation because the dimension are exactly the same (instead 1/2 dimension of high version).  This is part of optimizing process for your iAd project.

Hopefully that helps.

-Takayasu

I ran in to this yesterday.  I still do not know what caused it, but I thought I would share my journey to resolution. 

Both my standard-sized and 2x-sized files were created in Photoshop from the same .psd file at the 2x dimension size, which I ensured had even-numbered dimensions in both height and width.  The 2x file is created by saving the .psd as a .jpg and setting the jpg compression so that the resulting file size will be less than 250KB.  The standard file is created by applying a 50% image size reduction and saving it as a jpg file with compression such that the resulting file size will be less than 250KB.

In my iAD Producer project file, on the Assets pane I had right-clicked to Import... and selected the standard sized file and the @2x sized file ("Splash background.jpg" and "Splash background@2x.jpg").

Then I worked for many hours, many other asset imports, adding pages, actions, testing, etc.  Eventually I noticed when viewing the overview that my project had some warnings in the Properties pane of the Inspector.  The only one I could not resolve was the "Splash Background" had incompatible dimensions -- which made no sense.  I right clicked on it in the list of assets and chose "Reveal original in Finder" which preselected the two files and I showed the Get Info for both: As expected, the dimensions were both even and the @2x file had dimensions exactly 2x the standard file size.

Nothing I tried within my iAd Producer file would allow me to update the two files to clear the warning.

Eventually I started a new iAd Producer project and imported these two same files.  I applied them to the Shared Layers, Background, and there were no warnings.

Feeling vindicated but still stumped I switched focus back to my (still open) original iAd Producer project file and noticed right away that to the right of the asset listing for my "Splash Background" asset was the reload circular arrow!  I right-clicked, chose Update (which had never been available before) and the warning message went away.

The only original visual indication I had that something in iAd Producer was amiss was at the top of the Assets pane, where information about the selected asset is shown. On my "Splash Background" both the 1x and 2x files were listed with a file size of 185KB, which, if correct, would be a curious fluke of compression settings.  In fact, using Finder's Get Info I could see that the file sizes were 203KB and 236KB respectively.  After iAd Producer allowed me to Update the asset, the information about the selected asset showed correct file sizes for the two files.

So I can't really understand why importing the files in question into a new project caused the original project to notice it's understanding of the files didn't match what the files really look like, but maybe this little bit of voodoo will help someone else clear the warning they, too, are battling.