Posts

Post not yet marked as solved
7 Replies
2.5k Views
I have two different build configurations (Debug & Release), backed by their respective *.xcconfig file. The app also embeds an App Clip. Both build configs have a different Bundle ID, which are both registered properly in the dev center. Everything worked fine (I could have both configs installed and running on my phone as two separately identified apps) before I added the App Clip. Now since I added the App Clip, I cannot anymore compile my app properly in both configurations. I get different issues in either scenario and it has to do with my App Clip not matching either of the main app's build configurations. I think my problem boils down to my inability of making the App Clip's "Parent Application Identifiers" work both ways. If I set that to my main app's ID $(AppIdentifierPrefix)com.my.app I can build Release fine - which is what I currently fall back to - I live with the fact I can only debug with the Release config for now. If I set it to my debug app's ID $(AppIdentifierPrefix)com.my.app.staging I get The com.apple.developer.parent-application-identifiers entitlement ('["TEAMID.com.my.app"]') of an App Clip must match the application-identifier entitlement ('TEAMID.com.my.app.staging') of its containing parent app. If I just add both app ids there - since it's an array in the plist file, I get There can only be one parent application identifier associated with an app clip, but multiple parent application identifiers were found in the entitlement plist. I had tried to add different build configurations for the App Clip and setting its "Parent Application Identifiers" dynamically as $(AppIdentifierPrefix)com.my.app$(BUNDLE_ID_SUFFIX) where BUNDLE_ID_SUFFIX would be either empty or staging but that also didnt' work for a reason I don't really remember right now. The thing is - I don't even really need the App Clip in Debug, since it won't run anyway. Debug is never pushed to Apple, so the App Clip wouldn't ever work anyway. So maybe my actual question is: How can I just not include the App Clip at all in my Debug build?
Posted Last updated
.
Post not yet marked as solved
0 Replies
537 Views
Hey, I am confused about the value range returned here. According to the docs The returned value ranges from –160 dBFS, indicating minimum power, to 0 dBFS, indicating maximum power. However, I am seeing very loud values to be returned as > 0 routinely. Are the values being returned not actually dBFS and I need to do some calculation on those before? Essentially my issue is, that I want to normalize the value to a range between 0...1. I am using - what I understand to be - the typical dB to power conversion let linear = 1 - pow(10, recorder.averagePower(forChannel: 0) / 20) For values > 0, this returns values > 1 though, so my assumptions are not met. Cheers, Dennis
Posted Last updated
.