1 small note, it looks like you do still need to add <allowIndexDefinitions>true</allowIndexDefinitions>in your ui.apps pom.xml.  You don't need to do that to get it to pass the package type validation, but you do need it to pass the jackrabbit-oakindex validator!

I figured out how to handle this without downgrading.  Hopefully this helps you out too!You can actually resolve this issue without having to downgrade to version 1.0.4 of the filevault plugin.  The latest versions of the validator do take this situation into account (3.5.x) and you can override the...

To follow up on this, you can actually resolve this issue without having to downgrade to version 1.0.4 of the filevault plugin. I've created an article here with more details: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/deploying-oak-indexes-to-aem-as-a-cloud-service/m-...

In working with the Adobe support team, it seems I'm not the only one having these issues with AEMaaCS.  There is a ticket in the engineering backlog to deal with it, and not much we can do for now.  There's only 1 way I've found I can skirt the Adobe error page, which is to move error handling from...

Yeah, I'm working on it.  My Adobe Account Manager is attempting to schedule a meeting between Adobe I/O and CIF folks to work on triaging this.  It's an unbearable process, and it's taken over a week to get everyone on board here (and I still don't have a meeting on the books yet, hopefully that wi...

Just to follow up, my support requests are not actually getting routed to the Adobe I/O team.  I've had to reach out directly to the team in order to get any support, and they have requested our Adobe PM to engage them in a real capacity, but it would be really great if I knew the process for actual...

It's the same behavior in both author and publish, in both cases I get the screenshot (but in author I still get the author scaffolding and can edit page properties and such, where in publish I'm fully dead in the water and can't do anything. It works as expected locally though, with 500 errors, usi...

Hi everyone,I'm wondering if anyone has run into the Adobe 500 error page (aka error page of death), even when the ACS Commons error handler is enabled in AEM as a Cloud Service.  According to the docs on the ACS Commons page - see table of incompatible ACS Commons items on https://adobe-consulting-...

Thanks for your reply.  I have opened a support ticket but that team doesn’t handle Adobe I/O as far as I know.  Is there a way to open an Adobe I/O support ticket specifically?

Hi everyone, I'm having a pretty serious issue with Adobe I/O.  To give a little context, we’re using AEM to communicate with a commerce system via Adobe I/O.  We’re using the CIF OOTB framework to do so.  The long of the short is that once I deploy my Adobe I/O application, everything is happy and ...