I updated my BB10 DEV Alpha device for a firmware update on 10.2.For that I download the Dev Alpha B 10.2 from this url https://developer.blackberry.com/blackberry10devalpha/devalpha_update.html after which updated the device with the downloader as per the instructions given after the firmware updated my device didnt boot and became dead can anyone help me in this issue .
I have a BB10 DEV ALPHA A device.
Dev Alpha B update doesn't work for Dev Alpha as per I know. I have also tried to upgrade, but as it didn't worked I downgraded it to previous version.
Also, this is mentioned on BB Website.
Note: You may attempt to load the latest Dev Alpha B update onto your Dev Alpha A, however the The Dev Alpha A is no longer officially supported as of 10.1.0.1485. If you encounter any issues please downgrade back to 10.0.10.263 using the Autoloader method. You can download the old 10.0.10.263 Autoloader here.
https://developer.blackberry.com/blackberry10devalphas/update/
Related
Upon attempting to "Distribute App" archive in xCode, I get this error:
WARNING ITMS-90863: "Apple silicon Macs support issue. The app has LSApplicationLaunchProhibited set to true. This is not supported on Mac."
I have iPhone and iPad checked, but not MacOS. It is my understanding that stand-alone stickerpacks are not supported on Big Sur yet (nor has there been a hint that this will ever happen).
These projects were made using the StickerPack template in Xcode - not as an iMessage application - so there is zero coding involved on my end. I set the deployment target. I added the accessibility info - but that is it. I have no code on my end to toggle or fiddle with.
This is a VERY new error which surfaced as of Tuesday. I believe this is on Apple's end - some sort of update on their servers, because I had already successfully uploaded a stickerpack to the AppStore through AppConnect w/ the same version of Xcode a day before.
I already had 5 sticker packs published in the App Store for the past 3 years. I published updates to 2 of them literally just days ago. Then they had the Apple Event on Nov. 10 about Silicate macs and literally the next evening I got this error when trying to update another stickerpack.
I learned from previous errors before this that you need to make your product deployment target as 10.x because anything higher will give you a completely different error about 32 bit and 64 bit architecture. I dealt with that crap for over a week before I figured it out. That's what happens when you don't touch xCode for 2 years. Oops!
So after the error I cited showed up;
I tried creating a brand new version of the sticker pack from scratch that I was trying to update - since all I had to do was drag in my assets and re-type in all the accessibility tags for the visually impaired. Still no go.
So then, I updated to Big Sur - installation successful. Still no joy.
Then I updated Xcode after Big Sur. Successful updating, but still no joy.
I created a new archive w/ a different build number. Validated it successfully - but it failed AGAIN with the error I cited above. I've searched the Internet for an answer or a clue w/o success, but I think this is so new, a lot of people haven't figured this out yet. I'm waving my white flag now.
see the answer I posted to ITMS-90747: Basic sticker pack with no code, yet App Store Connect thinks there's 32bit code in there
(Apparently I'm not allowed to share the same answer to multiple posts about the same issue. Everyone is looking for this solution and I want it to be known!)
In short: You can opt out of the Apple Silicon Mac on the connect hub website, under availability and pricing
This is an app I'm helping out with remotely. I have some issues right after cloning repo..
Assets folder is marked as modified. git status results: modified: AppName/Resources/Images.xcassets/AppIcon.appiconset/Contents.json. One of many compile warnings says "A 1024x1024 app store icon is required for iOS apps". Is new 1024x1024 asset placeholder the modification that was made?
Many warnings:
The app is running well in App Store and has support for iPhoneX, so if I clone, shouldn't all this stuff be sorted out already? I still see layout issues when I run in simulator on any device size that were apparently fixed for iphoneX compatibility. When I was running Xcode 8.3 I didn't have these issues.
I need to add a feature, push and make build available on TestFlight, but I'm worried about pushing with all these compile errors & bet it wont even archive with missing 1024x1024 asset.
Question:
Should I just go back to previous version of Xcode rather than sticking with 9.1 or resolve all this stuff myself? Devs aren't really available for me to consult with since initial app was developed through full-service software dev company.
Im mainly in contact with business ops/project managers who don't really have knowledge of tech at this level. Im no seasoned dev myself so I'd like some advice here before expressing concerns with managers or getting strings pulled to talk with devs who last worked on it.
I'm hoping the first comment isn't that this question doesn't belong here. I think its a fine line.
Thanks for your time.
The app in the appstore could be submitted and released to the appstore with issues listed in the issue navigator of the xcode on posted screenshot.
So, switching to a version of Xcode which was used for a last submit to the app store by previous developers does not guarantee that those issues will be not present.
There is only one issue which you have to resolve is "1024x1024 app store icon is required for iOS app" and this can be done only within Xcode 9
The app is uploaded without errors, but when I press the install button I get this message:
I'm using macOS Sierra 10.12 and Xcode 8.
This has never happened to me in old versions of Xcode. What could be wrong?
TestFlight is currently unavailable, i can't either install from TestFlight or see any of my builds in Itunes Connect. Also my app was in processing for 4 hours, then this happened.
Please check here https://developer.apple.com/system-status/
or this screenshot
Update: Confirmed by Apple
I had the same issue. I never had an issue with setting or not setting the encryption flag. So I thought maybe they made a change today. So I added the key in and it still didn't work. I decided to remove the last build from testing then re-added it. That worked for me. I was immediately able to download and install the app. Hope that helps.
Build another version and upload to Itunes Connect.
Maybe your time uploading have some problem from Apple Server.
I have just checked.
Seems to be working for me this morning now. Incidentally Brad my app had GPUImage embedded in it so just for giggles I also added the "App Uses Non-Exempt Encryption." switch to the embedded GPUImage plist. Not sure if that was relevant.
I have an error -3 http 400 (the 18 of August 2016) when I try to upload my iOS app on Fabric.
To fix this issue, I tried to :
Check StackOverflow : first, second,
clean the build folder,
restart the Fabric desktop app (on mac),
update the framework SDKs,
==> got no luck.
Then I check the Fabric status : http://status.fabric.io/history , everything seems ok.
Then I tried with a dummy app that contains a pod, it worked !
So I tried to change the cable, change the internet connection, didn't work either.
Then I tried to downsize the app (about 60Mb) to 20 Mo, no luck here too. The connection seems to be cut at approximatively 5 Mb every time.
The only strange things I have seen are :
the archive list in Fabric for my app are periodically disappearing. To fix this, I need to build a new archive, The archive list will reappear.
Fabric seems to think that my SDK are always outdated and ask me to update to SDK 3.7.3 even if I do the update. I can see the update worked as I have some modified frameworks files in my git repository.
If someone can helps, it would be nice,
thanks.
I have the same problem...
I solve this!
The problem was the access rights to the app, the manager invited me to the app, and works... Good luck!
With the newest version of forge v1.4.49 when I try and test my IOS app from my windows comp the app installs but when I open it crashes.
I also tested using testFlight and get the same error. ( I get no error message as the console does not work in windows for debug, it just opens and then closes when I try and run the app )
I put the version back to version 1.4.48 and it works fine so I'm guessing it is something introduced in the newest version.
Thanks
Update: This is due to cross-platform line ending issues in the Python standard library: we deployed a fix on 18th July '13 which will fix all deployed platform versions.
Original answer:
The only iOS change that went into v1.4.49 was reading app entitlements information from your provisioning profile, rather than inferring it from active modules.
I'd recommend using the iPhone configuration utility to get the console output off the device: you may see a message about incorrect entitlements.
If the particular message doesn't help clear this up for you, get in touch at support#trigger.io, with your IPA and provisioning profile for us to check over.