SQPIT-776 fix Github action: create bump pull request have a title with jira ticket number

Bump framework(s) version for:

iOS allows you to select multiple images or videos to share simultanously. However, Wire doesn't respond well to this. Sharing one image works fine. When you share multiple, no visual feedback appears after a long pause and you return to the media selection screen. Meanwhile, when you open Wire it first looks like nothing is happening. After a short while (30 seconds or so) all of a sudden the images appear. However, it seems that Wire accepts a maximum of 5 images at the same time, but doesn't give any feedback when you send more, but just picks 5. It should give a popup stating that max 5 images can be shared at a time.

And the worst part: these five images do not get sent. The get a status of 'Sending' but they never are. And the state is hidden by default so you have to tap the images to find out they aren't sent. When you send new messages or images afterwards, these are delivered but the older images remain unsent.

You can get these stalled images to send by shutting down Wire and restarting it, that will trigger a new attempt apparently.

• Have an unread message
• The wire icon on the homescreen shows a litte "1" indicating that I received a message
• Go into the app
• Read the message
• Leave the app again
• Problem: The counter still shows a "1" while it shouldn't actually display anything.

A lot of times, I have to actually enter the app twice in order to reset the notification count, it usually doesn't work the first time.

What's new in this PR?

EVERYBODY THAT MERGED SOMETHING ON DEVELOP DURING THE LAST PERIOD PLEASE HAVE A LOOK

The scope of this PR is align the feature branch with the last changes of develop.

EVERYBODY THAT MERGED SOMETHING ON DEVELOP DURING THE LAST PERIOD PLEASE HAVE A LOOK

I already requested this through the contact form a while ago but I think it would be better off here, making it easier to track progress on this issue if there is any.

I really hate typing on portrait mode, the buttons are just too small for my fingers. Unfortunately Wire doesn't support landscape mode on iOS. I would really love support for this to be added.

Dear Devs, I'm just guessing the source of the problem here, but I'm willing to work with you to figure this out. What I think is that after Carthage fails to use binary the compilation fails because it's still using $PODS_ROOT variable instead of the replacement $SRCROOT. Obviously, when I run 'pod install' as asked, it runs fine but error stays the same. Here are the errors and the log.

Carthage bootstrap doesn't install most binaries due to "version mismatch" (which Carthage should allow for backwards compatibility, but that's another issue/bug):

*** Skipped installing Cartography.framework binary due to the error:
	"Incompatible Swift version - framework was built with 3.0.2 and the local version is 3.1."


*** Building scheme "VIMNetworkingFramework" in VIMNetworking.xcworkspace
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -workspace /Users/baseline/Desktop/2017/github/wire-ios/Carthage/Checkouts/VIMNetworking/VIMNetworking.xcworkspace -scheme VIMNetworkingFramework -configuration Release -derivedDataPath /Users/baseline/Library/Caches/org.carthage.CarthageKit/DerivedData/VIMNetworking/v6.0.2-wire-swift3.0.2 -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/wy/hy23j0d94s95gdwy2s1gdw380000gn/T/carthage-xcodebuild.GNM6gT.log

and here's the tail of that log file:

PhaseScriptExecution [CP]\ Check\ Pods\ Manifest.lock /Users/baseline/Library/Caches/org.carthage.CarthageKit/DerivedData/VIMNetworking/v6.0.2-wire-swift3.0.2/Build/Intermediates/VIMNetworkingFramework.build/Release-iphoneos/VIMNetworkingFramework.build/Script-BBCA0BBBE8FFE626CD6221D5.sh
    cd /Users/baseline/Desktop/2017/github/wire-ios/Carthage/Checkouts/VIMNetworking/VIMNetworkingFramework
    /bin/sh -c /Users/baseline/Library/Caches/org.carthage.CarthageKit/DerivedData/VIMNetworking/v6.0.2-wire-swift3.0.2/Build/Intermediates/VIMNetworkingFramework.build/Release-iphoneos/VIMNetworkingFramework.build/Script-BBCA0BBBE8FFE626CD6221D5.sh
diff: /../Podfile.lock: No such file or directory
diff: /Manifest.lock: No such file or directory
error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

** BUILD FAILED **


The following build commands failed:
	PhaseScriptExecution [CP]\ Check\ Pods\ Manifest.lock /Users/baseline/Library/Caches/org.carthage.CarthageKit/DerivedData/VIMNetworking/v6.0.2-wire-swift3.0.2/Build/Intermediates/VIMNetworkingFramework.build/Release-iphoneos/VIMNetworkingFramework.build/Script-BBCA0BBBE8FFE626CD6221D5.sh
(1 failure)

Thank you!

Checklist (please check before submitting)

• [ x ] I checked the existing issues, and the issue was not reported before.

The problem

Briefly describe the issue you are experiencing (or the feature you want to see added to Wire). Tell us what you were trying to do and what happened instead.

Environment

• Wire version that exhibits the issue: 3.49
• Last Wire version that did not exhibit the issue (if applicable): 3.48
• iOS version used to run Wire: 13.3
• iOS device type: iPhone SE
• Mobile network type (EDGE/LTE/Wi-Fi/Offline): any
• Exact date, time and timezone (only for the crash issues): at the moment of submitting this post and 15 minutes before (7JAN 06:50 GMT+2 ...)

Details

After updating to the newest version, wire was loading for 5-10 seconds (logo) and then crashed. Now it consistently crashes immediately upon opening. I have three different accounts logged in, all without a phone number.

Short description

When I open the wire app it takes 5 to 15 seconds that it shows my list of chats.

Behavior:

The opening of the app is between 5 and 15 seconds on a iPhone 5s with iOS 10. But some people I know have newer iPhone's (6 or newer) and the boot up is between 5 and 10 seconds.

Expected behavior

I suspect from a chat app it will load under 5 seconds on devices like the iPhone 5s and much faster on newer ones. And when I already have booted the app in the background the app should open nearly instantly.

What's new in this PR?

In this PR can find:

Application Launching Refactoring Issue Fix:

When the app was in background and then for some reasons were going in foreground the AppStateCalculator was forcing to load the appState. This is wrong cause if we have no variation in the appState this is not necessary and we don't have to force it. In fact in the scenario we were opening a deep link and the user was authenticated we were forcing the app to the same state it already was (.authenticated) and all the transition were performed and the ZMClientController were returning to its initial state and show the conversation list. Removing the force parameter the transition are not execute when not necessary.

DeepLink Sync-Engine communication Refactoring:

Regarding this topic see the PR https://github.com/wireapp/wire-ios-sync-engine/pull/1327

Dependenties

sync-engine: https://github.com/wireapp/wire-ios-sync-engine/pull/1327

Checklist (please check before submitting)

[ X] - I checked the existing issues, and the issue was not reported before.

The problem

No warning for a verified contact when adding a new device

Environment

• Wire version that exhibits the issue: 3.2
• Last Wire version that did not exhibit the issue (if applicable): N/A
• iOS version used to run Wire: 11.1.1
• iOS device type: iPhone SE
• Mobile network type (EDGE/LTE/Wi-Fi/Offline): Wifi
• Exact date, time and timezone (only for the crash issues): N/A

Details

• A is having a mobile 1
• B is having a mobile (iOS) and a desktop
• A is adding a new mobile to their account and send a message to B.
• A is sending a new message to B (see 1 below)
• B is answering with their Wire mobile.

There is no warning of losing the verified status (missed then the point of verifying contact). Similar to #440 and give even more credit to https://github.com/wireapp/wire-webapp/issues/208

• B continues the conversation on Wire desktop and the warning is displayed there:

Calling Debug logs (only for calling issues)

N/A

Screenshots

Cf. upper

The problem

If user already has an account, they are unable to log in via a freshly installed app.

Details

After selecting [phone] on the first screen and typing in the phone number, the screen moves to a different step of the process. Sometimes I can see the field to enter the 6digit code for a couple of seconds, sometimes I don't see it at all. In any case, when the SMS arrives 10 seconds later, it's always too late and screen has already moved to "Add your email and password." Please note there is no visible way to go back to previous screen from there and actually finish logging in. I also can't seem to find a "skip" button. Maybe it's hidden behind the keyboard?

ACC-384 [iOS] Fix Add participants screen in the dark mode

PR Submission Checklist for internal contributors

• The PR Title

  • [x] conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • [x] contains a reference JIRA issue number like SQPIT-764
  • [x] answers the question: If merged, this PR will: ... ³

• The PR Description

  • [x] is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

1. Checkmark is blue, but should have an accent color.
2. "Add participants" has wrong color in the dark mode.
3. Text color in the search field has wrong color in the dark mode.

Solutions

Add resolvedColor(with: traitCollection) to the color which should select the correct semantic color.

PR Post Submission Checklist for internal contributors (Optional)

• [ ] Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

• [ ] If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

PR Submission Checklist for internal contributors

• The PR Title

  • [x] conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • [x] contains a reference JIRA issue number like SQPIT-764
  • [x] answers the question: If merged, this PR will: ... ³

• The PR Description

  • [x] is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

With this PR we update the design of the Tab Bar to match our design specs.

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

PR Submission Checklist for internal contributors

• The PR Title

  • [x] conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • [x] contains a reference JIRA issue number like SQPIT-764
  • [x] answers the question: If merged, this PR will: ... ³

• The PR Description

  • [x] is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

After merging #5827, we missed a couple of spots and didn't update the colors for TextSearchResultLabel, TextSearchResultCell, TextSearchResultFooter. With this PR we update the colors for those classes and also make a couple of fixes on NoResultsView.

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

PR Submission Checklist for internal contributors

• The PR Title

  • [x] conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • [ ] contains a reference JIRA issue number like SQPIT-764
  • [x] answers the question: If merged, this PR will: ... ³

• The PR Description

  • [x] is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Since we started implementing accessibility changes into the app, we decided at some point to get rid of the UIFont+FontSpec file. With this PR we're one step closer to that direction. The first part is to remove the smallFont from that file and replace it with code from FontSpec.swift

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

ACC-143 Context change on focus (3.2.1)

PR Submission Checklist for internal contributors

• The PR Title

  • [ ] conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • [ ] contains a reference JIRA issue number like SQPIT-764
  • [ ] answers the question: If merged, this PR will: ... ³

• The PR Description

  • [ ] is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Figma

TODO: more tests

PR Post Submission Checklist for internal contributors (Optional)

• [ ] Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

• [ ] If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.