-
Notifications
You must be signed in to change notification settings - Fork 67
Custom name for Info.plist file fails to run tests #23
Comments
I have found issue. The reason is in "Prototype.app", I have custom app.name, bwoken doesn't check it in the script. |
Is there something bwoken should be doing in this case to make your life easier? Or is this issue resolved? |
I've also ran into this issue as my project/workspace name does not match the application name. @XBeg9 did you manage to get around this? |
@rdougan I'm not working with bwoken currently, it was just preview for my client. I change static text "Prototype.app" to my own target app.name. |
Same issue here... |
@rdougan @XBeg9 @zhanjingjie Could you explain in better detail what needs to happen for bwoken to work for you? Do you need a custom app name? Custom Info.plist name? |
I"m running into this issue and am not sure what needs to be done to have bwoken work (i'm using 2.0.1 beta), our plist has a custom name |
same issue here, |
Had the same issue. Adding "--product-name " to the bwoken command line solved the issue for me. |
If your project or target has non-standard name for Info.plist file, you will get this error and tests are stopped.
Any ideas how to fix this?
The text was updated successfully, but these errors were encountered: