Connor Tumbleson

> > @DAGpro - You'll want to fix CI issues here. Looks like a basic lint issue so the test suite can move forward. > > The commit message must...

> @iBotPeaches when will a fix be complete? I don't know - accepting any fixes or research.

Going to close this one for https://github.com/iBotPeaches/Apktool/issues/2890 I believe the path on this is wrong as the root issue is the new attribute splitter we introduced and not related to...

This was already resolved during the internal framework update. You could test yourself with a snapshot build here - https://github.com/iBotPeaches/Apktool/actions/runs/2644508403

Not sure right now. The resource is in the application, so it does point at Apktool messing something up. ``` ➜ 2849 aapt d resources AccuBattery_v1.5.1.1_apkpure.com.apk --values | grep '0x7f0c001c'...

I'm confused how I've been breaking this for years, but it appears the spec has caught with browsers in the enforcement. Probably happened around when Chrome started enforcing cookie lax/none....

> Hmm but we should transform the headers to just return the requested value: https://github.com/asm89/stack-cors/blob/88aaf08c68a66647309b7535f55591dc785b29ed/src/CorsService.php#L178-L187 > Will see if I can reproduce I see, so the array with asterik gets...

> Are you using 2.0.1 of stack-cors? "name": "asm89/stack-cors", "version": "v2.0.1", "name": "fruitcake/laravel-cors", "version": "v2.0.1",

> But it doesn't drop Authorization, that header is not requested by your `Access-Control-Request-Headers`? Correct, I'm not a true master at the understanding yet of all this CORS stuff. I...

> I would expect that the browser would take care of the Request-Headers values, you wouldn't have to do that manually. I'll do some low level nginx logging to get...