How can I archieve a subtask in Asana? It is easy to archive the task but I couldn't find a way to archive a subtask.
After searching here, I directed the question to #asana via Twitter and received the following reply: "no subtask archiving yet - but it’s on our list." See Twitter post at https://twitter.com/asana/status/280760677457608704
Related
I know its duplicate question, I want to update my app and after getting upload successful through the Xcode I can't see the new version...
I want to know how long it usually takes until ill see that? and if after I got upload successful could be another problem why its not upload? if yes what are the problems might be?
I updated the version and the build number, so its not the issue
thank you for the help
So I will post an answer since a comment is to short to answer this.
So the step for the release are:
Upload a build from Xcode
Wait for the build to be processed (this can take some time)
You will be notified by itunesconnect when the processing is done
In this stage the processing can already detect some issues with your app, like missing assets or something like that
You can check the status of your build in the activity tab
You won't get any "App Store status" until you actually release it. Now after the processing is done, you can select the build from the "My App -> App Name" in the "Build" section, there is a "+" that, in my opinion is placed very bad.
I upload my iOS app and most of the app metadata to iTunes Connect using fastlane deliver. Most of the data and screenshots can be put into files that I then have stored in git.
This includes for example the review notes that are stored in a file
fastlane/metadata/review_information/notes.txt
In iTunes Connect there is a bit of information in the TestFlight part under "Test Information" called "Beta App Description". I would like to also upload this text using fastlane.
In the fastlane deliver docs I have found the parameter called "beta_app_description" and as far as I can read, this is exactly that. This is a command parameter and as such muct be spefified directly in the Fastfile or Deliverfile.
I would like to have fastlane load this from a file just like all the other metadata.
Is this possible and how?
Besides deliver (or upload_ios_app) there is a testflight (or upload_to_testflight or pilot) action in fastlane:
https://docs.fastlane.tools/actions/testflight/
As the name suggests, it is used for everything Testflight, which includes the beta description:
beta_app_description | Provide the beta app description when uploading a new build
https://docs.fastlane.tools/actions/testflight/#parameters
pilot is also the name of a connected command line tool, that has additional options:
https://docs.fastlane.tools/actions/pilot/
Unfortunately, getting this data from a file is not part of any of those.
It can be easily provided as a parameter to testflight action.
And if you like to format your text or provide more than just a sentence, you can use groovy's multi-line strings, e.g.:
upload_to_testflight(
beta_app_description: "Have fun testing the app!",
changelog:
"""This is my multi-line changelog
with information for my testers.
* align left to avoid blanks at the beginning of a line
* this allows nice formatting...
* ...and blank lines in between
Hope, you find it useful."""
)
I am currently having issues validating and uploading my Xcode to itunesconnect. I have done it plenty of times before with other build numbers and now all of a sudden it will not work. I am using an opensource framework called SCLAlertView. Uploading my project with that framework in the past was fine but now it will not work. I have searched through just about every related thread from google and could not find a solution. The exact error is "Archive validation operation failed due to the issues listed below. iTunes Store operation failed. No suitable application records were found. Verify your bundle identifier 'org.cocoapods.SCLAlertView' is correct." I tried messing with the code signing identifier and provisional profile settings but nothing seems to be working. Also I would like to emphasize that the error is only given for the SCLAlertView framework, not my main application. I would appreciate any advice on how to fix this issue. Thanks in advance.
I have the error: "It looks like we are missing dSYMs to process crashes for the versions below." - I have downloaded the dSYMs in the Xcode organiser, found the .xarchive and zipped the corresponding dSYMs folder and uploaded with success; but the error does not disappear i.e. does nothing:
How can I symbolicate my crash reports?
dSYM Folder:
I just had the same issue and searching for solutions brought me here. Since this is missing an answer and I solved the issue for me, I'll resurrect this question to maybe help others having the same issue in the future.
Below the part shown in your first screenshot, there should be a list "REQUIRED (These are needed before crashes can be processed)" stating which UUIDs are still missing their dSYM and from which Build they are.
Just download the dSYM of the respective Build(s) like stated in the official Docs » Crashlytics » All about Missing dSYMs.
(E.g. log into iTunes, select the respective Build and click on download dSYM at the Build Details screen)
The downloaded dSYM(s) can simply be manually uploaded as you already did the other file(s).
I've tried almost all the variants, described here on stack overflow and on Fabric info page, to solve the same issue. But, unfortunately, none of them helped. And I've found a new solution, which I haven't seen here on Stackoverflow and which fitted me.
I've integrated HockeyApp with the project of my app and uploaded the build into HockeyApp (the build is uploaded there with an archive which contains dSYMs). After that the crashes started finally appearing on Crashlytics as symbolicated crashes with details.
I just had the same issue. The reason was enabled bitcode. So disable it or download dSYMs from iTC and upload them manually. I didn't find bette solutions yet.
I'm trying to upload a build on Itunes Connect, but the build is invalid every time. In Test Flight he appears like continuously processing.
See the pictures below:
I think this is Mac-OS(Sierra) related issue.I have Xcode-8 and Sierra, and getting "This build is Invalid" message and not able to share the build.
But when I upload the build by using Xcode-7 with "EL capita" then build processed, and I share that with other members.