android build non FLAG_SEC builds for internal use (screenshots) #449

Closed
opened 2022-04-28 16:01:09 +00:00 by dan · 0 comments
Owner
  • our designer is using apks built by prod with the prod signing key.

so this either looks like just install the prod signing key on a dev machine and manually make second builds of releases with the SEC_FLAG comnmented out and put in cloud

or investigate a way to automate it, with a simple shell script to comment it out and do a second "unsafe" build, but i dont love the idea of putting those in build.openprivacy.ca/files so we'd have to think about another deployment stage and to where and it would add like 10 more min to release build stages...

- our designer is using apks built by prod with the prod signing key. so this either looks like just install the prod signing key on a dev machine and manually make second builds of releases with the SEC_FLAG comnmented out and put in cloud or investigate a way to automate it, with a simple shell script to comment it out and do a second "unsafe" build, but i dont love the idea of putting those in build.openprivacy.ca/files so we'd have to think about another deployment stage and to where and it would add like 10 more min to release build stages...
sarah added this to the Cwtch Beta (In Progress) project 2022-05-24 19:24:32 +00:00
sarah added the
android
label 2022-05-24 19:24:35 +00:00
sarah closed this issue 2022-07-04 20:24:01 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtch.im/cwtch-ui#449
No description provided.