Deliver fails with "Unexpected Error" after uploading package to iTunes Connect

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Deliver fails with "Unexpected Error" after uploading package to iTunes Connect
It happened three time with three different apps after the last deliver update (v1.41.1)
Complete output when running fastlane, including the stack trace and command used
[14:10:07]: ---------------------
[14:10:07]: --- Step: deliver ---
[14:10:07]: ---------------------
[14:10:07]: Login to iTunes Connect (XXXXXXXXXXX)
[14:10:10]: Login successful

+--------------------------------------------------------------------+-----------------------------+
|                                      deliver 1.14.1 Summary                                      |
+--------------------------------------------------------------------+-----------------------------+
| force                                                              | true                        |
| submit_for_review                                                  | true                        |
| automatic_release                                                  | true                        |
| metadata_path                                                      | ./fastlane/metadata         |
| screenshots_path                                                   | ./calabash_screenshots      |
| app_icon                                                           | ./fastlane/../Framework/... |
| app_version                                                        | 1.2                         |
| release_notes.default                                              | Bug fixes. General stabi... |
| app_review_information.first_name                                  | XXXXXXX                     |
| app_review_information.last_name                                   | XXXXXXX                     |
| app_review_information.phone_number                                | XXXXXXXXXXXXXXXX            |
| app_review_information.email_address                               | XXXXXXXXXXXXXXXXXXXXXXXXXXX |
| app_review_information.notes                                       | XXXXXXXXXXXXXXXXXXXXXXXXXXX |
| price_tier                                                         | 0                           |
| copyright                                                          | XXXXXXXXXXXXXXX             |
| app_rating_config_path                                             | ./fastlane/./ratings.json   |
| submission_information.add_id_info_uses_idfa                       | false                       |
| submission_information.export_compliance_uses_encryption           | false                       |
| submission_information.export_compliance_encryption_updated        | false                       |
| submission_information.content_rights_contains_third_party_content | false                       |
| ipa                                                                | /Users/Shared/Jenkins/Ho... |
| username                                                           | XXXXXXXXXXXXXXXXXXXXXX      |
| app_identifier                                                     | XXXXXXXXXXXXXXXXXXXXXXXXX   |
| skip_binary_upload                                                 | false                       |
| skip_screenshots                                                   | false                       |
| skip_metadata                                                      | false                       |
+--------------------------------------------------------------------+-----------------------------+

[14:10:13]: Making sure the latest version on iTunes Connect matches '1.2' from the ipa file...
[14:10:14]: '1.2' is the latest version on iTunes Connect
[14:10:14]: Loading './fastlane/metadata/en-GB/description.txt'...
[14:10:14]: Loading './fastlane/metadata/en-GB/keywords.txt'...
[14:10:14]: Loading './fastlane/metadata/en-GB/release_notes.txt'...
[14:10:14]: Loading './fastlane/metadata/en-GB/support_url.txt'...
[14:10:14]: Loading './fastlane/metadata/en-GB/privacy_url.txt'...
[14:10:14]: Loading './fastlane/metadata/primary_category.txt'...
[14:10:14]: Loading './fastlane/metadata/secondary_category.txt'...
[14:10:14]: Detected languages: ["en-GB", "default"]
[14:10:15]: Activating language en-GB...
[14:10:17]: Uploading metadata to iTunes Connect
[14:10:18]: Successfully uploaded initial set of metadata to iTunes Connect
[14:10:19]: Starting with the upload of screenshots...
[14:10:19]: Uploading 5 screenshots for language en-GB
[14:10:19]: Uploading './calabash_screenshots/en-GB/iPhone6Plus_screenshot_0.png'...
[14:10:23]: Uploading './calabash_screenshots/en-GB/iPhone6Plus_screenshot_1.png'...
[14:10:26]: Uploading './calabash_screenshots/en-GB/iPhone6Plus_screenshot_2.png'...
[14:10:32]: Uploading './calabash_screenshots/en-GB/iPhone6Plus_screenshot_3.png'...
[14:10:34]: Uploading './calabash_screenshots/en-GB/iPhone6Plus_screenshot_4.png'...
[14:10:40]: Saving changes
[14:10:43]: Successfully uploaded screenshots to iTunes Connect
[14:10:44]: Price Tier unchanged (tier 0)
[14:10:45]: Uploading app icon...
[14:10:48]: Uploading binary to iTunes Connect
[14:10:49]: Going to upload updated app to iTunes Connect
[14:10:49]: This might take a few minutes. Please don't interrupt the script.
[14:11:38]: iTunes Transporter successfully finished its job
[14:11:38]: ------------------------------------------------------------------------------------------------------
[14:11:38]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[14:11:38]: ------------------------------------------------------------------------------------------------------
[14:11:38]: Finished the upload to iTunes Connect
[14:11:41]: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[14:11:41]: Variable Dump:
[14:11:41]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"deploy", :BUILD_NUMBER=>"There does not seem to be a CURRENT_PROJECT_VERSION key set for this project.  Add this key to your target's expert build settings.", :PRODUCE_APPLE_ID=>"1151383393", :CERT_FILE_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/CM68X7BFDE.cer", :CERT_CERTIFICATE_ID=>"CM68X7BFDE", :SIGH_PROFILE_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/AppStore_com.XXXXXXXX.XXXXXXXX.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/AppStore_com.XXXXXXXX.XXXXXXXXX.mobileprovision"], :SIGH_UDID=>"XXXXXXX-XXXXX-XXXXXX-XXXXX-XXXXXXX", :SIGH_PROFILE_TYPE=>"app-store", :IPA_OUTPUT_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/XXXXXXX.ipa", :DSYM_OUTPUT_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/XXXXXXXXXX.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2016-10-07/Framework 2016-10-07 14.08.45.xcarchive"}
[14:11:41]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}

+------+---------------------------------------------------------------+-------------+
|                                  fastlane summary                                  |
+------+---------------------------------------------------------------+-------------+
| Step | Action                                                        | Time (in s) |
+------+---------------------------------------------------------------+-------------+
| 1    | Verifying required fastlane version                           | 0           |
| 2    | team_id                                                       | 0           |
| 3    | increment_build_number                                        | 0           |
| 4    | produce                                                       | 13          |
| 5    | cert                                                          | 62          |
| 6    | sigh                                                          | 43          |
| 7    | git -C .. apply fastlane/stopAskLocation.patch                | 0           |
| 8    | git -C .. apply -R fastlane/stopAskLocation.patch             | 0           |
| 9    | open<EMAIL_ADDRESS> | 0           |
| 10   | [ -d /Volumes/Shared/Dropbox\ \(AppInstitute\)/AppInstitute\  | 0           |
| 11   | cp ../AppStore_com.* /Volumes/Shared/Dropbox\ \(AppInstitute\ | 0           |
| 12   | cp ../*.mobileprovision /Volumes/Shared/Dropbox\ \(AppInstitu | 0           |
| 13   | cp production_* /Volumes/Shared/Dropbox\ \(AppInstitute\)/App | 0           |
| 14   | update_project_code_signing                                   | 0           |
| 15   | gym                                                           | 84          |
| 💥    | deliver                                                      | 94          |
+------+---------------------------------------------------------------+-------------+

[14:11:42]: fastlane finished with errors```

### Configuration Files

Please copy the complete content of your `Fastfile` and any other configuration files you use below:

Fastfile:
```ruby
fastlane_version "1.105.0"

team_id "XXXXXXXXXXX"
ENV["FASTLANE_ITC_TEAM_ID"] = "XXXXXXXXX"

lane :deploy do |options|
  increment_build_number( build_number: "4447" )
  produce({
    	app_name: "XXXXXXX",
    	language: "UK English",
    	app_version: "1.2",
    	sku: "XXXXXXXX",
	team_name: "XXXXXXX Ltd"
  })
  cert

  sigh( force: true )

  ENV["SNAPSHOT_SKIP_OPEN_SUMMARY"] = "1"
  sh "git -C .. apply fastlane/stopAskLocation.patch"

  sh "git -C .. apply -R fastlane/stopAskLocation.patch"

  update_project_code_signing( path: "Framework.xcodeproj")

  ENV["FASTLANE_XCODE_LIST_TIMEOUT"]="120"
  gym(
    scheme: "Framework",
  )
  ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t Aspera,Signiant,DAV -m diagnostic"
  deliver(
	force: true,
	submit_for_review: options[:submit],
	automatic_release: options[:release],
	metadata_path: "./fastlane/metadata"
  )
end

Deliverfile:
screenshots_path "./calabash_screenshots"

basePath = "./fastlane/"
app_icon basePath + "../Framework/Resources/Images.xcassets/AppIcon.appiconset/icon_1024.png"

app ENV["PRODUCE_APPLE_ID"]
app_version '1.2' # you can pass this if you want to verify the version number with the ipa file

release_notes({
  'default' => 'Bug fixes. General stability updates.'
})

release_notes({
'default' => 'Bug fixes. General stability updates.'
})
app_review_information({
  first_name: ENV['BUILD_USER_FIRST_NAME'],
  last_name: ENV['BUILD_USER_LAST_NAME'],
  phone_number: "XXXXXXXXXXX",
  email_address: ENV['BUILD_USER_EMAIL'],
  notes: "The 'Listen Now' tab allows the user to play music from an audio stream hosted on the internet (http://XX.XX.XX.XX:8040/listen.pls).

Push notifications are used to:
* inform users when updates are available
* respond to forms submitted via the app
* notify a user when they receive any new messages from the Message Centre within the app
* send users notifications, user specific opt in offers, and loyalty points when they are in a specific physical location (geo-fencing), which requires access to the phone's GPS location

"
})

price_tier 0
copyright "#{Time.now.year} XXXXXXXXX"

app_rating_config_path basePath + "./ratings.json"

submission_information({
    add_id_info_uses_idfa: false,
    export_compliance_uses_encryption: false,
    export_compliance_encryption_updated: false,
    content_rights_contains_third_party_content: false
})

ipa ENV["IPA_OUTPUT_PATH"]

Environment
Jenkins version 2.7.2
MacOS X version 10.11.3
fastlane version 1.105.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
NO
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
NO

seems like it's not... I don't get any issue directly in Xcode

Just started seeing the same error as well, starting yesterday. We were able to deploy some 20 apps with no issue Thursday afternoon, with submission for review and everything.
Thursday night/Friday morning, we were able to upload but started getting Unexpected Errors on submission for review. Starting in the afternoon, we were seeing the same error as yours upon upload.
Just verified, and it's still there.
Relevant portion of our stack trace (seeing this both in Jenkins and on a local release):
/Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/spaceship-0.34.3/lib/spaceship/client.rb:453:in `parse_response': [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"} (Spaceship::Client::UnexpectedResponse)
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/spaceship-0.34.3/lib/spaceship/tunes/tunes_client.rb:299:in `app_version'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/spaceship-0.34.3/lib/spaceship/tunes/app_version.rb:174:in `find'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/spaceship-0.34.3/lib/spaceship/tunes/application.rb:102:in `edit_version'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/deliver-1.14.1/lib/deliver/submit_for_review.rb:32:in `select_build'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/deliver-1.14.1/lib/deliver/submit_for_review.rb:5:in `submit!'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/deliver-1.14.1/lib/deliver/runner.rb:87:in `submit_for_review'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/deliver-1.14.1/lib/deliver/runner.rb:30:in `run'
	from /Users/nmonasterio/.rvm/gems/ruby-2.2.3/gems/deliver-1.14.1/lib/deliver/commands_generator.rb:

Same here, exact stack trace.
I do not know if it has something to do but after (or before) this error https://itunesconnect.apple.com has a "500 Interval server error"...

Having the same issue as @nmonasterio. The stack trace looks exactly the same:
/Library/Ruby/Gems/2.0.0/gems/spaceship-0.34.3/lib/spaceship/client.rb:453:in `parse_response': [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"} (Spaceship::Client::UnexpectedResponse)
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.34.3/lib/spaceship/tunes/tunes_client.rb:299:in `app_version'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.34.3/lib/spaceship/tunes/app_version.rb:174:in `find'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.34.3/lib/spaceship/tunes/application.rb:102:in `edit_version'
	from /Library/Ruby/Gems/2.0.0/gems/deliver-1.14.1/lib/deliver/submit_for_review.rb:32:in `select_build'
	from /Library/Ruby/Gems/2.0.0/gems/deliver-1.14.1/lib/deliver/submit_for_review.rb:5:in `submit!'
	from /Library/Ruby/Gems/2.0.0/gems/deliver-1.14.1/lib/deliver/runner.rb:87:in `submit_for_review'
	from /Library/Ruby/Gems/2.0.0/gems/deliver-1.14.1/lib/deliver/runner.rb:30:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/actions/deliver.rb:18:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/runner.rb:202:in `block (2 levels) in execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/runner.rb:187:in `block in execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/runner.rb:186:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/runner.rb:186:in `execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/runner.rb:112:in `trigger_action_by_name'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.105.0/lib/fastlane/fast_file.rb:140:in `method_missing'
	from Fastfile:70:in `block (2 levels) in parsing_binding'

Fastfile:70 starts the deliver process.

Interesting, @dbalas . So, modifying your submission info hash did the trick?
Right now I have
{    add_id_info_serves_ads: false,    add_id_info_uses_idfa: false,    export_compliance_uses_encryption: false,    export_compliance_encryption_updated: false  }
I'll add these two and see if that makes any difference and report back...
   content_rights_contains_third_party_content: false,   content_rights_has_rights: false
Thanks!

@dbalas
thanks for your comment. It seems the problem is in the 'submission_information'
I used to have
submission_information({
    add_id_info_uses_idfa: false,
    export_compliance_uses_encryption: false,
    export_compliance_encryption_updated: false,
    content_rights_contains_third_party_content: false
})

I noticed that I should only keep one of the two export_compliance_uses_encryption OR export_compliance_encryption_updated depending on the app being submitted for the first time or updated
Even if the previous settings have been working for a long time, it seems now something changed.

@kmpnz Did this just start happening to you (i.e., was your deliver lane working until recently)? What options are you passing for the submission-info hash, BTW?
If that's the case that some parameters are now required, I might be able to put in a PR for this, @KrauseFx , so that we fill in any defaults when they're not passed. How does that sound?

@igorstimoli That did it. Nice work!
Let me know if you'd like a PR for that, then, @KrauseFx . Happy to handle.

A PR sounds good, thanks @nmonasterio

Hi All, I'm not sure that's the issue. I have just deployed three apps to the App Store, all updates and one of the apps was successful the other 2 failed, with the same error above, after upload. If fails exactly after upload and well before the Submission Information is triggered.
[18:06:25]: iTunes Transporter successfully finished its job
[18:06:25]: ------------------------------------------------------------------------------------------------------
[18:06:25]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[18:06:25]: ------------------------------------------------------------------------------------------------------
[18:06:25]: Finished the upload to iTunes Connect
[18:06:26]: -------------------
[18:06:26]: --- Step: slack ---
[18:06:26]: -------------------
[18:06:28]: Successfully sent Slack notification
[18:06:28]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}```

I think @gregk8288 is right
The one I found seems to be a problem, but not the only one.
This morning I had a failure and I found out that I had the correct submission_information settings for that app and I received an Unexpected error
 {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}
The I logged in iTunesConnect and the app was there, but the build was not processed yet, so at the point it failed it was certainly not ready for triggering the submission information

Agreed. We had submissions fail throughout the day yesterday. Same issue as everyone is experiencing.
For what it's worth, I think iTunes Connect might be having some issues itself. I was greeted with all sorts of 500 errors yesterday in the UI as well, and people are reporting that they have uploaded binaries through Application Loader only to find the .ipa disappear a few minutes later. (Will add link shortly.)
I'm going to try looking at some of the HTTP traffic when calling these methods through spaceship (e.g., find and others). Will let everyone know if I see something...
N
Sent from my Nintendo Gameboy

On Oct 11, 2016, at 3:49 AM, igorstimoli<EMAIL_ADDRESS>wrote:
I think @gregk8288 is right
The one I found seems to be a problem, but not the only one.
This morning I had a failure and I found out that I had the correct submission_information settings for that app and I received an Unexpected error
{"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}
The I logged in iTunesConnect and the app was there, but the build was not processed yet, so at the point it failed it was certainly not ready for triggering the submission information
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Looks like this issue is connected to 500 error on iTC. I can't update any app while I'm getting 500 on iTC. Fastlane can give {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"} on any step (produce, deliver). Also the strangest thing is when I upload binary only ( without app icon) all is working as expected. But as soon as icon uploaded to iTC it gives 500

Looks like this issue is connected to 500 error on iTC. I can't update any app while I'm getting 500 on iTC. Fastlane can give {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"} on any step (produce, deliver). Also the strangest thing is when I upload binary only ( without app icon) all is working as expected. But as soon as icon uploaded to iTC it gives 500

I'm receiving the same errors as well for each app I try and update.

@Wojcik I was able to replicate the issue with the icon vs. no-icon upload. Good find!

@igorstimoli @nmonasterio @kd8ssq @Wojcik Just wanted to let you know I reached out to the core team about this and we'll update on this thread. Is this related only to submission_info?

@TKBurner
The issue seems to be related to the submit for review process.
Even when the submission_info setting are correct the submission fails with unexpected error
Setting the submit_for_review to false allow fastlane not to fail because it skips the last submission step.
As said before, I've noticed that the failure occurs before the build is processed, so it seems that the submission_info are not processed yet at that point.
When the submit process works the output looks like
[12:24:25]: iTunes Transporter successfully finished its job
[12:24:25]: ------------------------------------------------------------------------------------------------------
[12:24:25]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[12:24:25]: ------------------------------------------------------------------------------------------------------
[12:24:25]: Finished the upload to iTunes Connect
[12:24:26]: Selecting the latest build...
[12:24:28]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:25:02]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:26:07]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:26:38]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:27:10]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:27:42]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:28:14]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:28:45]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:29:17]: Waiting iTunes Connect processing for build 1.0 (4436)... this might take a while...
[12:29:49]: Selecting build 1.0 (4436)...
[12:29:51]: Successfully selected build

But it is failing like this
[14:11:38]: iTunes Transporter successfully finished its job
[14:11:38]: ------------------------------------------------------------------------------------------------------
[14:11:38]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[14:11:38]: ------------------------------------------------------------------------------------------------------
[14:11:38]: Finished the upload to iTunes Connect
[14:11:41]: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[14:11:41]: Variable Dump:
[14:11:41]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"deploy", :BUILD_NUMBER=>"There does not seem to be a CURRENT_PROJECT_VERSION key set for this project.  Add this key to your target's expert build settings.", :PRODUCE_APPLE_ID=>"1151383393", :CERT_FILE_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/CM68X7BFDE.cer", :CERT_CERTIFICATE_ID=>"CM68X7BFDE", :SIGH_PROFILE_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/AppStore_com.XXXXXXXX.XXXXXXXX.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/AppStore_com.XXXXXXXX.XXXXXXXXX.mobileprovision"], :SIGH_UDID=>"XXXXXXX-XXXXX-XXXXXX-XXXXX-XXXXXXX", :SIGH_PROFILE_TYPE=>"app-store", :IPA_OUTPUT_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/XXXXXXX.ipa", :DSYM_OUTPUT_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/XXXXXXXXXX.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2016-10-07/Framework 2016-10-07 14.08.45.xcarchive"}
[14:11:41]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}

So we get an unexpected error just after the ipa is uploaded and before it is processed by iTunesConnect

For context, I've been looking at the payloads for uploading the app icon. Things seem to be pretty consistent, but comparing against the upload_file method here:
POST /upload/image HTTP/1.1 Host: du-itc.itunes.apple.com Connection: keep-alive Content-Length: 272778 Pragma: no-cache Cache-Control: no-cache X-Apple-Upload-ContentProviderId: xxxxx Origin: https://itunesconnect.apple.com User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Accept: application/json, text/plain, */* X-Original-Filename: ios-store-icon.png X-Apple-Upload-Validation-RuleSets: MZPFT.LargeApplicationIcon X-Apple-Request-UUID: xxxxx X-Apple-Upload-AppleId: xxxxx X-Apple-Upload-itctoken: xxxxx Content-Type: image/png X-Apple-Upload-Referrer: https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/xxxxx/ios/versioninfo Referer: https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/xxxxx/ios/versioninfo Accept-Encoding: gzip, deflate, br Accept-Language: en-US,en;q=0.8,es;q=0.6

FYI, I've started getting a 500 Internal Server Error from iTC when even trying to view my apps in the last few minutes.

I'm getting the same 500 Inernal Server Error on iTC as cdunkel above. Also althopugh I started having the same problem everyone else described here  I'm getting it immediately after a successful login to iTC when using fastlane.

@cdunkel @365SplendidSuns Saw those yesterday, too.

@cdunkel @365SplendidSuns Do you think this new issue is on Apple's side? It seems to be but I wanted to check with you. Either way we are looking into this. 👍 👍 💯

@TKBurner I'd be surprised if it wasn't Apple's side to be honest. Since my last post I've actually had one app submitted fine using deliver and another which failed after successfully selecting build with the error message "You must upload a large app icon" (My icons were fine).

@TKBurner It would seem so, especially given the fact that the payload currently being generated is just about identical. Do we have any insight on what the validation is (i.e., it might have changed)?

It seems that it is ITC.  I've had several times today where I've received 500 errors when I try to manage some of my apps.   I've also had trouble logging in and navigating around their interface.  Sometimes I receive a generic error message, other times I receive a 500 error message.

@TKBurner it definitely seems like Apple is a big part of it.  The only thing that I'm seeing that might not be Apple's fault is that if I'm doing back-to-back releases I can only make it through one run before I see this issue.  Re-running Fastlane then gets me through another app release.
That said, I've been seeing the same behavior as @kd8ssq.  iTC seems so unstable today that I'm amazed I'm getting anything through.

Same thing here, error signature looks the same and occurs randomly. Apple is preparing its 2017 April fools prank in advance.

@nmonasterio here are the options i'm using:
submission_information({
    add_id_info_uses_idfa: false,
    add_id_info_serves_ads: false,
    add_id_info_tracks_action: false,
    add_id_info_tracks_install: false,
    add_id_info_limits_tracking: false,
    content_rights_contains_third_party_content: true,
    content_rights_has_rights: true,
    export_compliance_is_exempt: true,
    export_compliance_contains_proprietary_cryptography: false,
    export_compliance_contains_third_party_cryptography: false,
    export_compliance_available_on_french_store: false,
    export_compliance_ccat_file: false,
    export_compliance_uses_encryption: false,
    export_compliance_app_type: false,
    export_compliance_encryption_updated: false,
    export_compliance_compliance_required: false,
    export_compliance_platform: false
})

Toggling content_rights_contains_third_party_content from true to false didn't help either

having too this problem

@GandjaFuzz @kmpnz @cdunkel @kd8ssq @365SplendidSuns @nmonasterio Any new findings? The team is looking into this! 👍 👍 👍

I've found that everything seems to upload properly, screenshots, metadata and the binary but as soon as it gets to the step where it's supposed to wait for the binary check to be complete, it fails.  The binary has still uploaded and after a few minutes I'll get an email that the processing is complete.  If I try to login to ITC around the time of the error, I'll get a 500 error when I click "My Apps".  After a few minutes I can view all the apps but I still get an error "We cannot process your request" if I try to view the newly uploaded app.  If I let it sit for about 20 minutes then I can get into the app and manually mark it for review and everything works.

@TKBurner My observations so far: Screenshots and the metadata are getting uploaded. The Transporter kicks in and according to the logs the binary should be uploaded as well, but I can't find in itunesconnect afterwards, even after a while. Here is a log snippet:
DEBUG [2016-10-12 13:43:40.25]: [Transporter]: DBG-X: Apple's web service operation return value:
DEBUG [2016-10-12 13:43:40.25]: [Transporter]: DBG-X:   parameter Success = true
DEBUG [2016-10-12 13:43:40.72]: [Transporter]: DBG-X: Unlocking token at path /Users/jenkins/.itmstransporter/UploadTokens/devmini.zurich.internal.xxxxxxx.io_ArnoFiva1027146839_1154498305.itmsp.token
DEBUG [2016-10-12 13:43:40.72]: [Transporter]: DBG-X: Releasing token file lock
DEBUG [2016-10-12 13:43:40.72]: [Transporter]: DBG-X: Removing token at path /Users/jenkins/.itmstransporter/UploadTokens/devmini.zurich.internal.xxxxxxx.io_ArnoFiva1027146839_1154498305.itmsp.token
DEBUG [2016-10-12 13:43:40.72]: [Transporter]: INFO: Done performing uploadDone notification to Apple.
DEBUG [2016-10-12 13:43:40.72]: [Transporter]: INFO: The package: /tmp/1154498305.itmsp has been successfully uploaded.
INFO [2016-10-12 13:43:40.88]: iTunes Transporter successfully finished its job
DEBUG [2016-10-12 13:43:40.88]: [Transporter]: DBG-X: Returning 0
INFO [2016-10-12 13:43:40.98]: ------------------------------------------------------------------------------------------------------
INFO [2016-10-12 13:43:40.98]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
INFO [2016-10-12 13:43:40.98]: ------------------------------------------------------------------------------------------------------
INFO [2016-10-12 13:43:40.98]: Finished the upload to iTunes Connect
INFO [2016-10-12 13:43:41.86]: -------------------
INFO [2016-10-12 13:43:41.86]: --- Step: slack ---
INFO [2016-10-12 13:43:41.86]: -------------------
INFO [2016-10-12 13:43:42.56]: Successfully sent Slack notification
WARN [2016-10-12 13:43:42.56]: Variable Dump:
INFO [2016-10-12 13:43:42.56]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios store", :BUILD_NUMBER=>"13", :SIGH_PROFILE_PATH=>"/Users/jenkins/workspace/clients/ios/appstore-ios-xxxxxxxx-store/AppStore_ch.xxxxxxx.xxxxxx.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/jenkins/workspace/clients/ios/appstore-ios-xxxxxx-store/AppStore_ch.xxxxxxx.xxxxxx.mobileprovision"], :SIGH_UDID=>"f3cbb476-7efa-4d94-88b0-2c309ec8194d", :SIGH_PROFILE_TYPE=>"app-store", :IPA_OUTPUT_PATH=>"/Users/jenkins/workspace/clients/ios/appstore-ios-xxxxxx-store/Products/XX_Talk-4.7.2b13.ipa", :DSYM_OUTPUT_PATH=>"/Users/jenkins/workspace/clients/ios/appstore-ios-xxxxxx-store/Products/XX_Talk-4.7.2b13.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/jenkins/Library/Developer/Xcode/Archives/2016-10-12/XX_Talk-4.7.2b13 2016-10-12 13.37.11.xcarchive"}
ERROR [2016-10-12 13:43:42.56]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}

Just this morning I've noticed when I try to create a new app in ITC using produce, it takes a very long time to create.  Most of the time my script times out, then I have to wait till I see the app created in ITC before I can continue.
[11:49:02]: Waiting for the newly created application to be available on iTunes Connect... [11:49:17]: Waiting for the newly created application to be available on iTunes Connect... [11:49:33]: Waiting for the newly created application to be available on iTunes Connect... [11:49:48]: Waiting for the newly created application to be available on iTunes Connect... [11:50:03]: Waiting for the newly created application to be available on iTunes Connect... [11:50:19]: Waiting for the newly created application to be available on iTunes Connect... [11:50:34]: Waiting for the newly created application to be available on iTunes Connect... [11:50:50]: Waiting for the newly created application to be available on iTunes Connect... [11:51:06]: Waiting for the newly created application to be available on iTunes Connect... [11:51:21]: Waiting for the newly created application to be available on iTunes Connect... [11:51:36]: Waiting for the newly created application to be available on iTunes Connect... [11:51:56]: Waiting for the newly created application to be available on iTunes Connect... [11:52:12]: Waiting for the newly created application to be available on iTunes Connect... [11:52:27]: Waiting for the newly created application to be available on iTunes Connect... [11:52:44]: Waiting for the newly created application to be available on iTunes Connect... [11:52:59]: Waiting for the newly created application to be available on iTunes Connect... [11:53:14]: Waiting for the newly created application to be available on iTunes Connect... [11:53:29]: Waiting for the newly created application to be available on iTunes Connect... [11:53:45]: Waiting for the newly created application to be available on iTunes Connect... [11:54:00]: Waiting for the newly created application to be available on iTunes Connect... [11:54:15]: Waiting for the newly created application to be available on iTunes Connect... [11:54:31]: Waiting for the newly created application to be available on iTunes Connect... [11:54:46]: Waiting for the newly created application to be available on iTunes Connect... [11:55:02]: Waiting for the newly created application to be available on iTunes Connect... [11:55:17]: Waiting for the newly created application to be available on iTunes Connect... [11:55:32]: Waiting for the newly created application to be available on iTunes Connect... [11:55:48]: Waiting for the newly created application to be available on iTunes Connect... [11:56:03]: Waiting for the newly created application to be available on iTunes Connect... [11:56:18]: Waiting for the newly created application to be available on iTunes Connect... [11:56:34]: Waiting for the newly created application to be available on iTunes Connect... [11:56:49]: Waiting for the newly created application to be available on iTunes Connect... [11:57:05]: Waiting for the newly created application to be available on iTunes Connect... [11:57:20]: Waiting for the newly created application to be available on iTunes Connect...

@TKBurner
still having the same issue.
I feel confident to confirm it doesn't depend on submission_info settings.
The problem is definitely on deliver submit_for_review step
Here is the output of my last try
+-------------------------------------------------------------+------------------------------------+
|                                      deliver 1.14.2 Summary                                      |
+-------------------------------------------------------------+------------------------------------+
| force                                                       | true                               |
| submit_for_review                                           | true                               |
| automatic_release                                           | true                               |
| metadata_path                                               | ./fastlane/metadata                |
| screenshots_path                                            | ./calabash_screenshots             |
| app_icon                                                    | ./fastlane/../Framework/Resourc... |
| app_version                                                 | 1.5                                |
| release_notes.default                                       | Bug fixes. General stability up... |
| app_review_information.first_name                           | xxxxxxxx                           |
| app_review_information.last_name                            | xxxxxxxx                           |
| app_review_information.phone_number                         | xxxxxxxx                           |
| app_review_information.email_address                        | xxxxxxxx                           |
| price_tier                                                  | 0                                  |
| copyright                                                   | xxxxxxxx                           |
| app_rating_config_path                                      | ./fastlane/./ratings.json          |
| submission_information.add_id_info_uses_idfa                | true                               |
| submission_information.add_id_info_serves_ads               | true                               |
| submission_information.add_id_info_limits_tracking          | true                               |
| submission_information.add_id_info_tracks_action            | false                              |
| submission_information.add_id_info_tracks_install           | false                              |
| submission_information.export_compliance_encryption_updated | false                              |
| ipa                                                         | /Users/Shared/Jenkins/Home/work... |
| username                                                    | xxxxxxxx                           |
| app_identifier                                              | xxxxxxxx                           |
| skip_binary_upload                                          | false                              |
| skip_screenshots                                            | false                              |
| skip_metadata                                               | false                              |
| dev_portal_team_name                                        | xxxxxxxx                           |
+-------------------------------------------------------------+------------------------------------+

[09:53:00]: Successfully uploaded screenshots to iTunes Connect
[09:53:02]: Price Tier unchanged (tier 0)
[09:53:03]: Uploading app icon...
[09:53:11]: Uploading binary to iTunes Connect
[09:53:12]: Going to upload updated app to iTunes Connect
[09:53:12]: This might take a few minutes. Please don't interrupt the script.
[09:54:28]: iTunes Transporter successfully finished its job
[09:54:28]: ------------------------------------------------------------------------------------------------------
[09:54:28]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[09:54:28]: ------------------------------------------------------------------------------------------------------
[09:54:28]: Finished the upload to iTunes Connect
[09:54:29]: Variable Dump:
[09:54:29]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"deploy", :BUILD_NUMBER=>"There does not seem to be a CURRENT_PROJECT_VERSION key set for this project.  Add this key to your target's expert build settings.", :PRODUCE_APPLE_ID=>"xxxxxxxx", :CERT_FILE_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/CM68X7BFDE.cer", :CERT_CERTIFICATE_ID=>"CM68X7BFDE", :SIGH_PROFILE_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/AppStore_com.xxxxxxxx.xxxxxxxx.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/AppStore_com.xxxxxxxx.xxxxxxxx.mobileprovision"], :SIGH_UDID=>"xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx", :SIGH_PROFILE_TYPE=>"app-store", :IPA_OUTPUT_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/Framework.ipa", :DSYM_OUTPUT_PATH=>"/Users/Shared/Jenkins/Home/workspace/iOS Build - Complete Release/iOS/Framework.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2016-10-14/Framework 2016-10-14 09.49.28.xcarchive"}
[09:54:29]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}

+------+---------------------------------------------------------------+-------------+
|                                  fastlane summary                                  |
+------+---------------------------------------------------------------+-------------+
| Step | Action                                                        | Time (in s) |
+------+---------------------------------------------------------------+-------------+
| 1    | Verifying required fastlane version                           | 0           |
| 2    | team_id                                                       | 0           |
| 3    | increment_build_number                                        | 0           |
| 4    | produce                                                       | 12          |
| 5    | cert                                                          | 60          |
| 6    | sigh                                                          | 46          |
| 7    | git -C .. apply fastlane/stopAskLocation.patch                | 0           |
| 8    | git -C .. apply -R fastlane/stopAskLocation.patch             | 0           |
| 9    | open<EMAIL_ADDRESS> | 0           |
| 10   | [ -d /Volumes/Shared/Dropbox\ \(AppInstitute\)/AppInstitute\  | 0           |
| 11   | cp ../AppStore_com.* /Volumes/Shared/Dropbox\ \(AppInstitute\ | 0           |
| 12   | cp ../*.mobileprovision /Volumes/Shared/Dropbox\ \(AppInstitu | 0           |
| 13   | cp production_* /Volumes/Shared/Dropbox\ \(AppInstitute\)/App | 0           |
| 14   | update_project_code_signing                                   | 0           |
| 15   | gym                                                           | 99          |
| 💥    | deliver                                                       | 204         |
| 17   | echo "[RaiseError/]{"reference": "fastlane_deploy","errorData | 0           |
+------+---------------------------------------------------------------+-------------+

[09:54:29]: fastlane finished with errors

I've been having the having this same issue the past 2 days. I forgot to save my output, but it's identical to @igorstimoli above. The ipa successfully uploads and then fastlane fails.
I also noticed that when I try to view the app in ITC I get a 500 error saying "We can't process your request." After about 30 minutes of waiting it finally stops throwing the error in ITC.
Attached the report.xml
report.txt

I've been seeing the problem for about as long as @ChrisVolentine.  It's nice to know that I'm not alone, haha.
Unlike some of the other people in this thread I'm only seeing the error in the produce phase of the lane, not deliver.  I have yet to have a problem uploading the binary, but about every 15-45 minutes my deliver step fails with the same error listed above.
Just for reference, this is my output:
+----------------+---------------------------------------+
|               Summary for produce 1.2.1                |
+----------------+---------------------------------------+
| username       |<EMAIL_ADDRESS>     |
| app_identifier | com.xxxx.xxxx |
| app_name       | xxxxxxx                 |
| language       | English                               |
| app_version    | 4.1.0                                 |
| sku            | xxxxxxxx                            |
| skip_itc       | false                                 |
| skip_devcenter | false                                 |
+----------------+---------------------------------------+

[10:24:47]: [DevCenter] App 'com.xxxx.xxxx' already exists, nothing to do on the Dev Center
[10:24:50]: Variable Dump:

<HUGE JSON DUMP HERE>

[10:24:50]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"}
Users/xxx/.rvm/gems/ruby-2.2.2/gems/spaceship-0.34.3/lib/spaceship/client.rb:453:in `parse_response': [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Unexpected Error"], "info"=>nil}, "statusCode"=>"ERROR"} (Spaceship::Client::UnexpectedResponse)
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/spaceship-0.34.3/lib/spaceship/tunes/tunes_client.rb:201:in `applications'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/spaceship-0.34.3/lib/spaceship/tunes/application.rb:56:in `all'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/spaceship-0.34.3/lib/spaceship/tunes/application.rb:62:in `find'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/produce-1.2.1/lib/produce/itunes_connect.rb:59:in `fetch_application'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/produce-1.2.1/lib/produce/itunes_connect.rb:16:in `create_new_app'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/produce-1.2.1/lib/produce/itunes_connect.rb:12:in `run'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/produce-1.2.1/lib/produce/manager.rb:8:in `start_producing'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/actions/produce.rb:19:in `block in run'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/actions/produce.rb:17:in `chdir'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/actions/produce.rb:17:in `run'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:202:in `block (2 levels) in execute_action'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:187:in `block in execute_action'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:186:in `chdir'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:186:in `execute_action'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:112:in `trigger_action_by_name'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/fast_file.rb:140:in `method_missing'
	from Fastfile:203:in `block (2 levels) in parsing_binding'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:165:in `try_switch_to_lane'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:120:in `trigger_action_by_name'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/fast_file.rb:140:in `method_missing'
	from Fastfile:304:in `block (3 levels) in parsing_binding'
	from Fastfile:302:in `each'
	from Fastfile:302:in `block (2 levels) in parsing_binding'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/lane.rb:33:in `call'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/runner.rb:45:in `execute'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/commands_generator.rb:244:in `run'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/commands_generator.rb:20:in `start'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/gems/fastlane-1.105.0/bin/fastlane:5:in `<top (required)>'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/bin/fastlane:23:in `load'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/bin/fastlane:23:in `<main>'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/bin/ruby_executable_hooks:15:in `eval'
	from /Users/xxx/.rvm/gems/ruby-2.2.2/bin/ruby_executable_hooks:15:in `<main>'

I put together a ruby script that uses Spaceship to finish submitting an app for review if the deliver fails right after upload as it seems to for most of us.
https://gist.github.com/zineer/17a516aeebc16cd731190f26184d01e2
You'll need to make at least a few tweaks to match your purposes including

replace your email into line 56
change the submission properties on lines 73-87 to match your submission_information from your Deliverfile

Then you can chmod +x finishfailed.rb, and run it like ./finishfailed com.domain.app
It is based on https://github.com/fastlane/fastlane/blob/master/deliver/lib/deliver/submit_for_review.rb but for getting the app and edit_version it catches the exception caused by the 500 error and loops until the error goes away, then continues with the submission.

Thanks for this, @zineer ! So, what you're saying is that, even with your existing submission_information payload (before this issue), you were able to just keep trying and trying and it would eventually work?

@nmonasterio Correct. I noticed that (at least in my case) after Deliver failed with "Unexpected Error", logging into iTunesConnect in my browser to view the new app would also throw errors, but within a minute or so I would be able to view the app. Then trying to view the version would throw another error, but it also went away within a couple minutes and I was able to see the build that was delivered was successfully uploaded and was processing. Once the build was finished processing, I was able to select it and submit the app for review. So the script I wrote above basically just handles that process which I was doing manually.
I use another custom build script which handles creating Cordova apps for me and calls Fastlane as part of that, so I just have it check the exit code from fastlane and run my script from above when a failure code is found. You could probably build my script into a plugin and do a begin/rescue in your Fastfile.

Hi everyone!
We are going to hold off on trying to write a fix/workaround for this for the time being as this is something that is happening on Apple's end (given that they are displaying 500's on the web) and we expect them to fix it in the not-so-distant future.
In the mean time, we would encourage you to submit issues to iTunesConnect's support center with reports that this happens even when uploading via the web UI.

For the moment I applied this inelegant change to the SubmitForReview class in deliver/submit_for_review.rb
    def submit!(options)
      app = options[:app]
      ####### here starts the change #######
      # set a timer
      start = Time.now
      UI.message("Trying to select the build...")
      # start a loop to try multiple times
      loop do
        begin
          select_build(options)
          # if select_build doesn't return any error break and continue normally
          break
        rescue
          # if select_build fails output a message and retry after 60 secs
          UI.message("")
          UI.message("Trying again...")
          if (Time.now - start) > (60 * 2)
            UI.message("#{((Time.now - start) / 60).round} minutes passed...")
          end
          # if still failing after 20 minutes will abort
          if (Time.now - start) > (60 * 20)
            UI.message("it's taking too long!")
            UI.message("Aborting.")
            raise "Error while trying to select the build in iTunesConnect."
          end
          sleep 60
        end
      end
      ####### here ends the change #######

      UI.message("Submitting the app for review...")
      submission = app.create_submission

      # Set app submission information
      # Default Values
      submission.content_rights_contains_third_party_content = false
      submission.content_rights_has_rights = true
      submission.add_id_info_uses_idfa = false

      # User Values
      if options[:submission_information]
        options[:submission_information].each do |key, value|
          UI.message("Setting '#{key}' to '#{value}'...")
          submission.send("#{key}=", value)
        end
      end

      # Finalize app submission
      submission.complete!

      UI.success("Successfully submitted the app for review!")
    end

it's based on @zineer script concept, but applied directly to deliver source code
@ohwutup waiting for a better solution from your side I want to let you know that trying this with four apps the average waiting time has been 5 minutes before deliver was able to select the build and exit the loop. After that everything worked properly

ITC returns 500 when uploading an icon and save.
The JSON for icon looks like this:
"largeAppIcon": {
        "value": {
            "assetToken": "Purple71/v4/cd/f9/f6/cdf9f60d-8c39-4c29-e5b4-c49a664714ad/pr_source.png",
            "sortOrder": null,
            "type": null,
            "size": 80012,
            "width": 1024,
            "height": 1024,
            "checksum": aiwkjed82idksiw,
            "originalFileName": "icon.png"
        }
    }

Before Apple made change to ITC, we only need to change assetToken and originalFileName part, leave the rest nil. But after Apple made the change, it will cause 500 error.
The solution is simply provide assetToken, originalFileName, size, width, height and checksum in the JSON. It will work. Leave the fix for @KrauseFx

@sunboshan Interesting. I did compare the payloads last week and didn't see anything different per se. I hadn't thought about newly required fields. Have you tested passing the extra parameters? If so, what did you base your checksum hash on? (The other three should be easy additions.)
It should be an easy PR, unless @KrauseFx wants to handle it directly.
Good find!

I did speak to a member of Apple developer support, especially since I was getting 500 errors in the iTC web UI whenever I would try to view my apps immediately after a Fastlane failure.  He did confirm that they have been speaking with other developers who were seeing a similar issue, so they were reasonably confident that it was a systemic issue on their end.  It does seem to be intermittent, though, so it sounded like they're having trouble tracking it down.
If I hear more back from them I'll post it here.

@nmonasterio the checksum should be based on the binary of the image file(not 100% sure though). Yet you don't need to get those information by yourself. After upload the image by sending POST request to https://du-itc.itunes.apple.com/upload/image, you will get response like this:
{
  "token" : "Purple71/v4/4e/3c/f1/4e3cf119-13a0-65b3-f7f2-f7cb824cb0d8/pr_source.png",
  "tokenType" : "AssetToken",
  "type" : "MZLargeApplicationIconType.SOURCE",
  "width" : 1024,
  "height" : 1024,
  "hasAlpha" : false,
  "length" : 61037,
  "md5" : "d41d8ed98f00b204e9800998ecf8427e"
}

@KrauseFx already has the fix for screenshot files in #6423, need to do similar fix for icon files. This has been tested for bunch of apps, providing assetToken, originalFileName, size, width, height and checksum will fix the 500 error.

Thank you for the insight, @sunboshan . I can confirm that by leaving out the app_icon option from deliver the submission succeeds without any errors. Would be great if this could get fixed.

Hi @GeovationMax Thanks for following up. I notified the core team that this issue is still present. 👍

I've also been seeing the same errors: 500s and "We can't process your request." pages for some of the apps we update/create.
I've been submitting for review manually to see if that helps. However, today I'm starting to see newly created apps take exceptionally long to appear on ITC. I've had the counter in Produce::ItunesConnect#create_new_app run out and throw Couldn't find newly created app on iTunes Connect - please check the website for more information. Anyone seeing the same?

Hey everyone, thanks for all the reports, and sorry it took so long. Thanks to @sunboshan, it was easy to reproduce the issue and provide a fix. I've just pushed https://github.com/fastlane/fastlane/pull/6652, which we'll merge and release as soon as possible :rocket:
We'll update this GitHub issue once the new version is live ✨

deliver 1.14.3 has been released with the fix! 🚀

Can confirm it works here.

Op 21 okt. 2016, om 20:13 heeft Andrea Falcone<EMAIL_ADDRESS>het volgende geschreven:
spaceship 0.36.1 has been shipped which resolves this issue. You can update to it by running:
gem update spaceship. Please let us know if this resolves this issue for you. 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/fastlane/fastlane/issues/6455#issuecomment-255436110, or mute the thread https://github.com/notifications/unsubscribe-auth/ABjMuKGjPt8BTMiXZTkaL8ceUMFJbLInks5q2QDigaJpZM4KREpL.


TestHarness API locatorFor is not working for ShadowDOM Element

Reproduction
Below is the code snippet where we created an Angular Element and Written TestHarness for that Angular Element.
angular-element-example.component.html

angular-element-example.component.ts
import { Component, ViewEncapsulation } from '@angular/core';
@Component({
templateUrl: './angular-element-example.component.html',
styleUrls: ['./angular-element-example.component.css'],
encapsulation: ViewEncapsulation.ShadowDom
})
export class AngularElementExampleComponent
{
Message = "Message from AngularElement";
constructor() {   }
}
AngularElementTestHarness.ts
import { ComponentHarness } from '@angular/cdk/testing';
export class AngularElementTestHarness extends ComponentHarness
{
static hostSelector = 'angular-element-example';
private heading1 = this.locatorFor('h1');
public async headingText(): Promise
{
const trigger = await this.heading1;
return (await trigger()).text();
}
}
Below is the Element Hierarchy in Inspect Tool.

Actual Behavior
When I try to run below test we are getting error as
Error: Failed to find element matching one of the following queries:
(TestElement for element matching selector: "h1")

As h1 is in #shadow-root, AngularElementTestHarness could not able to locate h1
private heading1 = this.locatorFor('h1');
Same is the case when we use TestHarness for any WebComponents developed in lit-element or Polymer.
Expected Behavior
AngularElementTestHarness should be able to locate h1 even h1 is in #shadow-root
private heading1 = this.locatorFor('h1');
PS:
In Angular Element (angular-element-example.component.ts) if I change the encapsulation as below then TestHarness is working as expected.
encapsulation: ViewEncapsulation.None
Environment

Angular: 9.0.2
CDK/Material: 9.1.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu):  Windows

Thanks. That's a great issue! We've added support for a custom querySelectorAll method. You could then use a library like kagekiri to query for harnesses in a shadow-piercing way. See: https://github.com/angular/components/pull/18178


Custom iL2CPP Thread il2pp_thread_attach

Hmm, the game crashes when i call some functions for example WorldToScreenPoint
but when I hook these functions they work fine any fixes for this?

I knew about this issue since beginning, but never bother to look futher since I have no clue why it happens and especially with different functions.
At the moment I just prefer to hook function like OnUpdate of some class or Camera render function and just do stuff there.
If you really need to do like World2Screen stuff, then you could take look at matrixes and just read them from Camera and calculate the screen position, instead calling the function.

Anyone who still has problem with this I need some tests on diff games as result:
void* m_pThisThread = IL2CPP::Thread::Attach(IL2CPP::Domain::Get());
/*

Run your code here...

*/
IL2CPP::Thread::Detach(m_pThisThread);

Instead creating new thread via API create it yourself and run this code in the loop so it attach and deattach.

I did do this a while back and came back to it, it had no effect, I tested it on a mobile game(CriticalOps) and terraria il2cpp steam game, I read some where a dude said he fixed his crashes by calling the il2cpp_thread_attach everytime he was ready to call a Unity function, personally I don’t think this function dose anything useful.

Seems weird since I tried to do simple ESP by just filtering out objects by certain name and calling Camera WorldToScreen function and I got the thread error and after doing attach and doing same thing and detaching it, it didn't popup error anymore.

Seems weird since I tried to do simple ESP by just filtering out objects by certain name and calling Camera WorldToScreen function and I got the thread error and after doing attach and doing same thing and detaching it, it didn't popup error anymore.

Well i tried it as you said to me and i can confirm it does work 100%, tested on Naraka BladePoint no crash/GC Collecting from unknown thread anymore so i guess this is an appropiate fix since i am doing like that on present and yei all works and the best part is i don't need the hook anymore.

Seems weird since I tried to do simple ESP by just filtering out objects by certain name and calling Camera WorldToScreen function and I got the thread error and after doing attach and doing same thing and detaching it, it didn't popup error anymore.

Well it seems to work I tested it on another game and it worked hahaha no idea what’s happening I guess this is the best way to use this attach method welp dipping thanks for all the help and the tool very helpful

re-check the repo , added callback way to use OnUpdate

Thank you guys for your work, this need update looks dope.

Closing this because callbacks has been added and it is easier to use than threads.


create React and Truffle project

create project soc-rec-wallets

Resolved via #11 and #12

Resolved via #11 and #12

Good job initializing the project! Only recommendation is to move the truffle initialization outside of the react app.

Thanks for reviewing it. Truffle initialization had been put inside to react app per earlier discussion (tasks.md) -
"1. Set up Truffle project
2. React project inside of it

use this truffle config:

https://github.com/MatricksDeCoder/Fojini-DEX
Look at line 27 and 28"
The benefit of having contracts folder inside react's src folder is so that react files have instant access to the latest abis without having to manually copying over abis whenever there's change in smart contracts.

Good job initializing the project! Only recommendation is to move the truffle initialization outside of the react app.

Thanks for reviewing it. Truffle initialization had been put inside to react app per earlier discussion (tasks.md) -
"1. Set up Truffle project
2. React project inside of it

use this truffle config:

https://github.com/MatricksDeCoder/Fojini-DEX
Look at line 27 and 28"
The benefit of having contracts folder inside react's src folder is so that react files have instant access to the latest abis without having to manually copying over abis whenever there's change in smart contracts.


[📚] Flutterfire docs edit link broken

The "Edit this page" link in this part of the Flutterfire docs is broken:
https://user-images.githubusercontent.com/1061209/208078647-ddc92170-ba09-43b7-8987-a380a7a7d5d0.mp4

@darshankawar Ah, my bad. The problem is that an individual page doesn't show the link. So if I have a link to any page within the documentation, I wouldn't know it's archived. Is it possible to display the archive notice on every page?

Not sure if that will be done any time soon, considering that domain is now archived and your best bet is to refer the new domain I linked earlier.
With that being said, I am going ahead and closing this issue. If you disagree, write in comments and I'll reopen it.


Add support for ittapi measurement

This will likely suffer from the same issue as https://github.com/JuliaCI/GCBenchmarks/pull/50, where the first collection (before callbacks are set) is not traced by the tool.


Update Getting Started readme to use qooxdoo compiler

When following https://github.com/qooxdoo/qooxdoo/blob/master/docs/README.md it says to install @qooxdoo/framework and then type qx to start the qooxdoo compiler, but that does not work because the framework package does not have the compiler binary. It should instead be to install @qooxdoo/compiler like in https://qooxdoo.org/documentation/6.0/#/development/compiler/

Hi, the README in the master branch reflects the v7 release of qooxdoo, in which the compiler has been merged into the framework. This is different from the v6 release which you are referring to. If you want to use the master branch for development, you need to build the compiler as described here: https://github.com/qooxdoo/qooxdoo/blob/master/docs/development/contribute.md#coding-the-framework


Submit to Firefox Addons Store

This extension works in temporary installation. 🎉
We should follow the steps to submit it to the actual Firefox Add-On store.

Submitted and now live! https://addons.mozilla.org/en-US/firefox/addon/copy-tab-link/


Webcam detected but not working

After install macOS Monterey on my Dell G5 (RTX 2060 rev) with your EFI Build and make it dual boot with Windows 11 22H2 I got problem with Webcam, both Windows and Mac are detected (in Windows Device Manager and Mac System Report) but:

Windows Camera show no camera connected.
Photobooth show blackscreen and camera light binking.
I try to change from OC 0.9.2 to OC 0.9.3 DEV no ACPI but no luck
Windows Camera show blackscreen.
Photobooth show blackscreen.
In Hackintool app, USB tab:
Intergrade webcam show at HS05 port, as internal type but it's always blinking

What can I do to fix this?
Thanks!

Are you loading windows with OpenCore? I recommend load windows with BIOS selection, because ACPI changes may impact other OSs. I use OpenCore exclusively to load macOS and load Windows using BIOS, pressing F12 when Dell logo appears. You may have to manually add the correct boot entry at BIOS setup.
Your issue could be hardware related, since it happen with every OS and the webcam is automatically detected by macOS, didn't need any extra work with OpenCore to detect it.
My webcam is detected as Integrated_Webcam_HD and yours is detected as USB 2.0 Camera. Maybe your camera hardware is different somehow too.

First try to load Windows using BIOS bootpicker and test webcam, then report back.

Check if your Thunderbolt configuration match the Readme.md, Hackintool will detect it as JHL6340 Thunderbolt 3 USB 3.1 Controller (I don't think this will relate to webcam, but I'm trying to match your setup as close to mine as I can)

I think you're right. But on my laptop, MacOS and Windows dual boot on the same disk (follow Dortania Multiboot Guide) so only have one EFI partition. BIOS boot picker only have one option to boot from my SSD and it boot to Opencore Picker.
I tried to add another boot entry for Windows but i'm not found any Windows bootx64.efi, just have one bootx64.efi from Opencore package.
Your guide may be work correctly in case dual boot on 2 disk. One use Opencore bootx64.efi and one use bootx64.efi from Windows Installation.
PS1: I install Windows after instal MacOS and follow manual instal guide (use command line and extract install.wim package), not standard installation steps.
PS2: At the first time boot into MacOS (without Windows Installed) my webcam detected as Integrated_Webcam_HD but after install Windows, device name change to USB 2.0 Camera on both Windows and Mac.
PS3: Can you tell me something about what's new in next release?
Thanks in advanced for your support!

Look for \EFI\Microsoft\Boot\bootmgfw.efi to boot Windows. I don't know if your EFI partition will have this file, since you used another method to dual boot.
You can try a Live Linux USB stick like Ubuntu. It won't load from your EFI partition, so you can test your webcam from there. I use Etcher to create a bootable USB.
The next release will be an update release (update OpenCore and kexts to new version). I don't think it will impact anything relevant in this machine. There's 2 issues I couldn't find a solution yet (external mic via headphone jack input and macOS freezing when remove and insert power cable a couple times) and it won't come in next release.


Forklift emits Last Insert Date as an event

Currently Forklift writes the Last Insert Date directly to Redis, then Discovery API retrieves that value directly from Redis when displaying a dataset to a user.
Forklift should emit an event with the Last Insert Date, including the dataset ID, the last insert date, and any other relevant data.
Discovery API should consume the Last Insert Date event and update its view state accordingly.
AC:

Forklift emits a Last Insert Date event
Forklift does not write Last Insert Date directly to Redis
Discovery API consumes Last Insert Date event and updates its view state
Discovery API displays the Last insert date based on its View state, not based a value Forklift inserted into Redis

TN:

It might be possible that this information is already captured by events currently being written to the event stream. If that is the case then Discovery API should consume that instead and Forklift should cease writing to Redis.

Is this related to an existing "event" that is already happening and being emitted such as "ingest:end"? If so, can this value just be included as an element of that value that is stored in forklift view state as part of the event?

That's what the tech note is about

The existing events are close, but not entirely ideal. It looks like our best bet in the arena would be data:extract:end, which, unfortunately does not necessarily indicate that data has been successfully written to Presto.
We're going to put in an event send where it the redis write would have been in the Forklift pipeline writer implementation.
Otherwise, we plan on merging the timestamp into the Dataset Model on event receive for Discovery API.


MI - TRANSPORTS (MailTo)

Complete [1].
[1] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/references/transports/mailto-transport.md

Fixed:
https://ei.docs.wso2.com/en/latest/micro-integrator/setup/transport_configurations/configuring-transports/#configuring-the-mailto-transport


Support for openAPI playground

Is your feature request related to a problem? Please describe.
In former days we used a hardcoded yaml in resources from the ktor generator for api documentation and now we switched to kopendium, but before we could host a openApi Playground using the openAPI route plugin thingens:  https://ktor.io/docs/server-openapi.html#configure-swagger
The problem is that for this you need a file, but we don't have that with kopendium
Describe the solution you'd like
I have already looked into the source code of the openAPI and found out that we probably might have to copy this function and adapt it using the generated kopendium documentation. The problem is that we need an event or so to notice when all routes are indexed so that we can start generating.

Just noticed that this is already possible using swagger. See this code line: https://github.com/bkbnio/kompendium/blob/fa96923a5a117c5f14eb0e8692dc3d89ce8855ee/playground/src/main/kotlin/io/bkbn/kompendium/playground/EnrichmentPlayground.kt#L57


Add Kaplan Open Source (Israel)

Hey, thank you! Is there an English version of the webpage?

There isn't. I would keep the Hebrew one.


Update README.md

Added Hacktoberfest contributing guideline link  to the Demos ReadMe, ready for approval? @CaroFG
Pull Request
What does this PR do?
Updating the documentation for Hacktoberfest 2022
PR checklist
Please check if your PR fulfills the following requirements:

[ ] Does this PR fix an existing issue?
[ ] Have you read the contributing guidelines?
[ ] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

May I suggest putting this section just below the main heading?

Thanks very much for the suggestion, it's done : )


ddev auth ssh

Describe the bug
Not able to execute ddev auth ssh
To Reproduce
Steps to reproduce the behavior:
$ ddev auth ssh
Unable to find image 'drud/ddev-ssh-agent:v1.10.1-built' locally
docker: Error response from daemon: manifest for drud/ddev-ssh-agent:v1.10.1-built not found.
See 'docker run --help'.
Docker command 'docker [run -it --rm --volumes-from=ddev-ssh-agent --user=1000 --mount=type=bind,src=~/.ssh,dst=~/.ssh drud/ddev-ssh-agent:v1.10.1-built ssh-add]' failed: exit status 125

Expected behavior
It should work
Screenshots
N/A
Additional context

Thanks for the report! Could you please ddev poweroff and then start again?

That fixed it.


Acquaintance gates

Towards #735

The 2to3 error is because range(...)[x:] gets translated into xrange(...)[x:] and xrange doesn't support slicing. Put a list around range to fix it.

The range was already being cast as a list.

Sorry about the flailing to fix the 2to3 error; I don't know how 2to3 works and I still can't run check.py locally because of that git error.

Is the 2to3 error because of the type of indices or shift?

What git error are you referring to?
Are you able to run ./python2.7-generate.sh? That will produce the python 2 code, and then you can cd into python2.7-output and (in a python2 virtual env) test out the code.

Any suggestions for this NamedTuple business? I just cannot make mypy happy.

Okay, I think I got everything.

Ah, I've misplaced that file. Please open an issue with a copy of the log.
You might find the tools we've been adding under check/ to be useful, e.g. check/pylint will run pylint with the appropriate configuration against the needed files.

Opened #787. The check stuff is very useful.

Done.


User without add stack permission can add blocks to global areas

How to reproduce:

Install the newest c5 from dev branch
patch the related files with the fix from #8390
Create a new user group "editor"
give the new group (editor) edit permissions on the page
give some "add block" permissions (custom, e.g. content and hoizontal rule)
save dialog, save also the related dashboard page (/dashboard/blocks/permissions)
remove the "add stack" permission from the new group (editor) if it was set
save dialog, save also the related dashboard page (/dashboard/blocks/permissions)
Create a new user
Add the new group (editor) to the new user
Log in as the new user
Edit the page
Add a content block to the global area "Footer Legal"
Save and approve the edited page
View the page with a different user

Results:

The block on the global area could be added
The page could be approved
A different user can see the block in the global area

Conclusion:

A user who is assigned only to the previously created editor user group should not be able to add a block to global areas.

This issue is an extract of https://github.com/concrete5/concrete5/pull/7989#issuecomment-512653022.

Confirmed with recent 8.5.x branch.
If I revert #8390 , the issue resolved.
The best result is fixing both issues, but if we can't, please just revert #8390 .
IMO this issue is more serious than #8244 😕

I'm not sure I understand. What issue is reverting #8390 meant to fix? This issue?

Yeah, reverting #8390 can fix this issue.

Please don't revert #8390 (it fixes another bug).
I'll try to find some time to check this #8401

@mlocati Any updates?


bugs & suggestions - wallhack, skills, sound issues, item/container ESP

i can split this post if needed ..
1) Wallhack
since diferent types of wallhack (box / skeleton / charms / infos) have diffewrent impact ont the performance and visibility of the AI would it be possible to split certain setting (xray, max distance) betwen them ?
RN Xray option only apply to Charms (bug ?) and distance applies to all at once
also we are forced to use fill color for skeleton/box so its impossible to have ONLY charmy outlines + box visible at the same time, could box/skeleton/info be switched to use outline color instaed of the fill color ?
example how it coould look like:
ShowBoxes
BoxDistance
BoxThicknes
BoxXray
ShowCharms
CharmsDistance
CharmsXray
etc..
2) Skills & sounds?
there seems to be some problems with skills
it does NOT give mastery 3 to all weapons even after using it multiple times (screenshot)

sound bug ?? when i get all the skills i become totaly silent, i think it has to do with skill CovertMovement but that one should reduce noise i make by 60% but i dont make any noise at all, i dont hear my steps at all, i dont hear movement/sprint/jumps on any surface ... is it caused by the game (the skill is bugged) or the trainer or am i supposed to be ninja ?
could there be some additional setting for the "skill" so we can choose what skills to level and how far ?
EDIT: found it, the  trainer maxes unlisted skills  named BotReload and BotSound,  those should be removed froom the trainer
3) container ESP
would it be possible to add under STASH a toggle to show other types of containers ?
airdrops, toolboxes, jackets, weapon boxes, etc ...
the idea here is to show all the searchable containers without having to use item tracking (cause that can be realy laggy)
also since those containers dont wanish would it be possible to change the cache for those so it cashes ALL of those at the beginning of raid and only shows it when you are within the maximum distance ? liek to remove the need to refresh cache
basicly make it like with wallhack, only shows within max distance but thee is no need for aditional cashing (lagging)
4) loot tracking Xray
RN tracking loot automaticlyhas Xray on , would it be possible to make it like with wallhack so there is xray setting so we can only track items that are in line of sight ?
basicly imagine tracking ALL items but only in line of sight (up to max distance), could that reduce the performance impact of tracking all (when i track all within 10m its still noticable 20+FPS drop no matter the cache time)
5) just question in general regarding cache time ... what to set it to for gamestate and wallshot ? what do those actualy do and how often should they be refreshed ? i understand that with items/grenades etc you want to update the ESP as soon as possible but what does gamestate and wallshot caches actualy do ? wallshot especialy gets the game realy lagy so is 30s ok ? is it just to load the armor on enemies so it knows it can bypas it or do i need to refresh it more often (and have laggy experience) ?

Regarding Skills and noise, indeed it seems BotReload and BotSound are special cased and not part of displayed skills:

it does NOT give mastery 3 to all weapons => I guess it's because you have pmc skills and scav skills. Perhaps using the feature on both profiles will do the trick.

For now you can always just use an spt aki profile editor if you really want to change skill levels etc.
Wallshoot is in the description on the main page

wallshoot
Shoot through wall/helmet/vest/material with maximum penetration and minimal deviation/ricochet.


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^7.2.1 remove ^7.2.0 (devDependencies.c8)

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add iffar.edu.br

@gabrhahn Please provide us with:

the school official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the school
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the school recognizes the domain which you are submitting as an official email domain for the students.

https://iffarroupilha.edu.br/
https://sig.iffarroupilha.edu.br/sigaa/public/curso/portal.jsf?id=66658 or https://www.iffarroupilha.edu.br/noticias-sb/item/3497
https://sig.iffarroupilha.edu.br/sigaa/public/curso/noticias_desc.jsf?id=66658&noticia=6661123 or https://sites.google.com/iffarroupilha.edu.br/email/como-ativar

De: Philip Torchinsky<EMAIL_ADDRESS>Enviado: quinta-feira, 13 de agosto de 2020 11:51
Para: JetBrains/swot<EMAIL_ADDRESS>Cc: Gabriel Hahn<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Assunto: Re: [JetBrains/swot] Add iffar.edu.br (#8810)
@gabrhahnhttps://github.com/gabrhahn Please provide us with:

the school official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the school
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the school recognizes the domain which you are submitting as an official email domain for the students.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/JetBrains/swot/pull/8810#issuecomment-673525039, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKNVGN4SGVRZHGDQWYDBE3DSAP4YLANCNFSM4PU53KRQ.
[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png]http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail     Livre de vírus. www.avg.comhttp://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail.

https://iffarroupilha.edu.br/

https://sig.iffarroupilha.edu.br/sigaa/public/curso/portal.jsf?id=66658 or https://www.iffarroupilha.edu.br/noticias-sb/item/3497

https://sig.iffarroupilha.edu.br/sigaa/public/curso/noticias_desc.jsf?id=66658&noticia=6661123 or https://sites.google.com/iffarroupilha.edu.br/email/como-ativar

@gabrhahn Thank you for the clarification. Pull request merged.


is the package name correct

In http://mvnrepository.com/artifact/com.io-informatics.oss/jackson-jsonld
there is the sensible com.io-informatics.oss » jackson-jsonld
but the actual package names appear to have a typo:
ioinformarics.oss.jackson.module.jsonld.annotation.JsonldId;

doesn't really cause any harm but the effect is a bit jarring

btw, neat library, seems v useful


Error during WebSocket handshake: Unexpected response code: 403

Using directLine or Webchat with my bot
After 5 minutes of using the bot i get a Websocket error.
authentication.service.ts:85 WebSocket connection to 'wss://directline.botframework.com/v3/directline/conversations/49zS5PwGN3TFWlfLAgKoKz-us/stream?watermark=-&t=ew0KICAiYWxnIjogIlJTMjU2IiwNCiAgImtpZCI6ICJ2cG4yYXhuRjFSU3NHUXg5aXd0WGEwZTNjRWciLA0KICAieDV0IjogInZwbjJheG5GMVJTc0dReDlpd3RYYTBlM2NFZyIsDQogICJ0eXAiOiAiSldUIg0KfQ.ew0KICAiYm90IjogIlBNRS1Cb3QtRCIsDQogICJzaXRlIjogIjl4TEU5aTVncEx3IiwNCiAgImNvbnYiOiAiNDl6UzVQd0dOM1RGV2xmTEFnS29Lei11cyIsDQogICJuYmYiOiAxNjMzNjk1NDAwLA0KICAiZXhwIjogMTYzMzY5NTQ2MCwNCiAgImlzcyI6ICJodHRwczovL2RpcmVjdGxpbmUuYm90ZnJhbWV3b3JrLmNvbS8iLA0KICAiYXVkIjogImh0dHBzOi8vZGlyZWN0bGluZS5ib3RmcmFtZXdvcmsuY29tLyINCn0.ScI-lSR2R1mQ3yUda7sYYJCU--hy6m0yLAgWgF0sEQ80-o6r90tvkBIJ8olR4mPJZxBbRTsnUnREXr-Bc61LM6OsjDGqa0kkJsA8jlF5Sw00wBrXND2PUGsWcauBppd6FRHmp5qhrivQQ9IpgnqRevkG8rVyIKUOi_-lbQz1AwWWHxxbpqfrRWKFvjyZplhDDL81i7dWYXQZRQn24LyWRgRVppdQcJHIFP5u5Zhcb37rp-6ElO7cRJULE6DCx73lg1rHjpeBzVDPKzAbSZWu8jt628qgIGYNVPRHqiCS05NXnGBkO-RJY0dwvUZ1nEVFTWsU79MEm6QTS4mVyZ9dHw' failed: Error during WebSocket handshake: Unexpected response code: 403
If I let the chat window open everything is fine. When i close the chat windows and then reconnect to the conversation the websocket error appear and the history isn't comming back. The chat still work but if i close it again the history is not saved anymore to the conversation.
I used postman to lisen to the websocket stream and i can see everything pass. When I try to connect to a stream after 5 minutes(after the websocket error), i got this message
Error: Unexpected server response: 403
Handshake Details
Request URL: https://directline.botframework.com/v3/directline/conversations/1xmoTM750ySKSoi8JvxNMV-6/stream?watermark=-&t=ew0KICAiYWxnIjogIlJTMjU2IiwNCiAgImtpZCI6ICJ2cG4yYXhuRjFSU3NHUXg5aXd0WGEwZTNjRWciLA0KICAieDV0IjogInZwbjJheG5GMVJTc0dReDlpd3RYYTBlM2NFZyIsDQogICJ0eXAiOiAiSldUIg0KfQ.ew0KICAiYm90IjogIlBNRS1Cb3QtRCIsDQogICJzaXRlIjogIjl4TEU5aTVncEx3IiwNCiAgImNvbnYiOiAiMXhtb1RNNzUweVNLU29pOEp2eE5NVi02IiwNCiAgIm5iZiI6IDE2MzMzNTk5OTUsDQogICJleHAiOiAxNjMzMzYwMDU1LA0KICAiaXNzIjogImh0dHBzOi8vZGlyZWN0bGluZS5ib3RmcmFtZXdvcmsuY29tLyIsDQogICJhdWQiOiAiaHR0cHM6Ly9kaXJlY3RsaW5lLmJvdGZyYW1ld29yay5jb20vIg0KfQ.tNDu_5s4FhPHxhKNjsaXB6t5OVHZ1z6jMto9olBXIVmt4myAP_Gw--RsS3B6cuR5roL9n5fPPo_gUVWye8SsYG9Y28yKheVAnFto6XlD2e5Ew-llJr4fXmpQW9sXDcO_lp4oLsWvWogj33xH7ua1smP6oEZ9ZvfKl1XrTW2E0fpplPKzZPJsal3iBKVseRIRisPIQqcZSD-Dw9dmJWfcy-MWW1j78pumDCk-p4p6Dpts4yGH-v_oguaVcB-1-6bnSuwxljIbcFGtHc6jRE5acriCrCWFvcER99BoHHxvTHOfHBDmBFrjLPx2nsxV7hOaLpAsx8N4p8XkRaIGM_owDw
Request Method: GET
Status Code: 403 Forbidden
Request Headers
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: 07TEu7JXBDayOkiMgA/l8g==
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Host: directline.botframework.com
Response Headers
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 88
Content-Type: application/json; charset=utf-8
Expires: -1
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
ARR-Disable-Session-Affinity: true
Date: Mon, 08 Oct 2021 15:13:14 GMT
I tried to make a loop to send a message each 60 seconds on my website with a secondary direct line connection to the same credentials. I wanted to find out if it's en idle problem and it's not.
      this.mySubscription= interval(environment.webSocketPingDelay).subscribe((x =>{
            let directLine = window.WebChat.createDirectLine({
                token: this.storageService.token,
                webSocket: environment.payload.webSocket,
                conversationId: this.storageService.conversationId,
                streamUrl: this.storageService.streamUrl
            });

        directLine.postActivity({
            from: { id: Authentication.user, name: "USER_NAME" },
            name: "keep_alive",
            type: "message",
            Text: "Keep"
        }).subscribe();
      }));

Since the web socket address indicate that the websocket is hosted on azure. "wss://directline.botframework.com/v3/directline/conversations/***"
On my azure channel i see no option to configure websocket.
On my webapi i used this configuration in my startup.cs
var webSocketOptions = new WebSocketOptions()
{
KeepAliveInterval = TimeSpan.FromSeconds(120),
};
app.UseWebSockets(webSocketOptions);
How can i configure it to last more than 5 minutes ?

Hi @GLDev21
It should be possible to reconnect to an existing conversation https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-direct-line-3-0-reconnect-to-conversation .  However, reconnecting is not a matter of using the same wss, but calling the reconnect api.
However, based on your description there might be some misunderstanding.  The websocket from WebChat is actually connected to just the DirectLine service, there is not a socket all the way to the bot (so the webapi socket connection timeout is not relavent).
@compulim please review

@compulim any update on this?

No, we are still having the issue, no answer to my 12oct question, No news from compulim

Your streamUrl lifetime does not expire as far as I know except when you lose connection, what happens e.g. with a page refresh. In this case you have to call the reconnect api to retrieve your chat history.


Fix race in StreamChannelCodecs()

This fixes issue 2 of #294. The root cause is that the lock held when accessing obj.Streams is immediately released and doesn't cover accesses to the channels map.
To quote:

The loop body locks the mutex and retrieves an instance to the streams:
obj.mutex.RLock()
tmp, ok := obj.Streams[streamID]
obj.mutex.RUnlock()

However, the channels map is accessed immediately after when the mutex is not held, which can easily result in crashes. This seems to be the root cause of #69,

To fix this somewhat elegantly, wrap the block that needs to access to the map in a function and hold the lock for the entire duration of the function.

thank you


[Feature Request]:  Add Kenyan quotes

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add quotes  by famous Kenyans
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

1 quote only.