Is there any way you could post it on this page so that others can benefit?  Thank you so much!

Yeah, it's very strange that styles for each field type (text, dropdown, etc.) have to be consistent across the DOR.

I haven't found a solution yet, I thought maybe updating to Sp16 would help, but tables still look the same in my custom DOR templates:If I use the 'Default' template the table looks correct: 

I have the exact same issue. I'm on 6.5.13. I don't see any errors in the logs either.  Did you ever figure this one out?

This is happening to me as well.  We're on 6.5.13. I don't see any relevant errors in our logs either.  

I realize I'm replying to an old thread, but I'm running into a similar issue. The styles applied to AF_TABLEITEM_XFO in our Base DOR template do not seem to translate into the generated PDF. In my use case the user is filling in fields that are not in a table, but we've change the settings of that ...

We've been troubleshooting this with Adobe support for a few weeks, and were finally able to perform the AEM/Sign integration successfully, but we had to jump through a few hoops.   For anyone encountering the 'failed to get refresh token' error, first try disabling Minification in Adobe Granite HTM...

Yes! We have /v2 at the end of the URL and are using the correct Sign shard in the url (na2).     I have a ticket open on this and folks are working on it. 

We're trying this integration on 6.5.13 (SP13), so I'm surprised we're still running into issues.  

Were you able to get past the 'Failed to get refresh token' error?  I'm also seeing 'nulloauth' values for the refresh token and access token URI's.  We're on a different shard than you, https://secure.na2.echosign.com/public/oauth/v2, and the redirect URI we're using in the Adobe Sign config seems ...