Post

Replies

Boosts

Views

Activity

Reply to Apple application rejected because of few references to a pre-release version of Apple software
if we want to release the application which is ios16 ready then what approach should be followed? What should be updated in metadata? There are a few things that you must never mention in the app metadata. In particular, things like this will be rejected by Apple: Includes a workaround for a bug in iOS. Supports a new iOS version that's still in beta. Can now share data with our Android app. Some previously paid features are now free. The solution is simple, just don't mention those things. Write a vague "what's new" message like "Miscellaneous bug fixes".
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’22
Reply to Apple API - How to update in-app purchase prices/create new purchases
This might get you a bit further: https://developer.apple.com/documentation/appstoreconnectapi/add_a_scheduled_price_change_to_an_in-app_purchase It's still lacking a lot of the details you will need..... If I were trying to do this, and assuming that there is no useful answer on StackOverflow, I'd try the "get price schedule" endpoint to get the current price info, and see if that data can be suitably modified and sent back to that "schedule price change" endpoint. Or maybe there is a WWDC video with some examples? (Please let us know if you get this working. I'm also a former user of the XML API, and I may have to do this at some point.)
Topic: App & System Services SubTopic: StoreKit Tags:
Sep ’22
Reply to Xcode 14 update has bugs and my code in c++ is not compiling with memory issues.
#include<bits/stdc++.h> #define int long long int Those two lines are ..... unconventional??! Does it still fail if you instead #include specific headers for vector, iostreams etc. and use a non-reserved-word (e.g. "Int") for your long long int macro? How exactly are you compiling it? Edited to add: After you've changed your #define to Int not int, change the signature of main back to int main.
Sep ’22
Reply to W-8BEN How to fill Part II, line 10. "Special rates and conditions"?
I think the more important part of their email is the one that I quoted, saying "Non-US residents and non-US legal entities are not required to provide a US tax ID." That conflicts with my experience, which was a few years ago. I don't have anything to add to what I said earlier. I got a US Tax ID for my business, which was not difficult, and used it to complete the form. Apple now tell you that that is not necessary. Either what I did was unnecessary, or they are wrong, or something has changed. I don't know which. You might consider following their advice and find yourself a local tax advisor with suitable experience who can tell you what to do.
Sep ’22
Reply to Xcode 14 update has bugs and my code in c++ is not compiling with memory issues.
Here is the simplified version of above code with the same issue:- Works for me on macOS 12.5, ARM, Xcode 14.0.0. Sorry, I'm not going to install the 12.6 beta just to check this!!! Remind me when it is released and I'll try again. Those two lines have nothing to do with this issue as I have been using them since years. Indeed they are probably nothing to do with the issue, but they're still very unconventional and you should not use them. The fact that something has been working for years doesn't mean that it's right, by any means! I would also suggest that you turn on warnings (-W and possibly -Wall). They don't report anything in this case, but it's still good practice.
Sep ’22
Reply to Xcode 14 update has bugs and my code in c++ is not compiling with memory issues.
Please compile the newer version of code anywhere other than Xcode. MacOS version does not matter. XCode version should be 14.0.0. That's what I did; I copied&pasted the code in your reply "here is the simplified version of the code" above into a file, and compiled on the command line with the g++ invocation exactly as you indicated in an earlier comment. It compiles without error. Note again that I'm using macOS 12.5 on ARM. My guess is that there is something odd in your environment. For example, since you're the sort of person who is happy to #define int :-) , do you have any shell aliases set up? Is g++ actually an alias for something else? Suggestion for how to debug this: run g++ --verbose and compare with what I get: % g++ --verbose --std=c++17 -W -Wall solution.cpp Apple clang version 14.0.0 (clang-1400.0.29.102) Target: arm64-apple-darwin21.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang" -cc1 -triple arm64-apple-macosx12.0.0 -Wundef-prefix=TARGET_OS_ -Wdeprecated-objc-isa-usage -Werror=deprecated-objc-isa-usage -Werror=implicit-function-declaration -emit-obj -mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name solution.cpp -mrelocation-model pic -pic-level 2 -mframe-pointer=non-leaf -fno-strict-return -fno-rounding-math -funwind-tables=2 -fobjc-msgsend-selector-stubs -target-sdk-version=12.3 -fvisibility-inlines-hidden-static-local-var -target-cpu apple-m1 -target-feature +v8.5a -target-feature +fp-armv8 -target-feature +neon -target-feature +crc -target-feature +crypto -target-feature +dotprod -target-feature +fp16fml -target-feature +ras -target-feature +lse -target-feature +rdm -target-feature +rcpc -target-feature +zcm -target-feature +zcz -target-feature +fullfp16 -target-feature +sm4 -target-feature +sha3 -target-feature +sha2 -target-feature +aes -target-abi darwinpcs -fallow-half-arguments-and-returns -debugger-tuning=lldb -target-linker-version 819.6 -v -resource-dir /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/14.0.0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -I/usr/local/include -stdlib=libc++ -internal-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1 -internal-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local/include -internal-isystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/14.0.0/include -internal-externc-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -internal-externc-isystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include -W -Wall -Wno-reorder-init-list -Wno-implicit-int-float-conversion -Wno-c99-designator -Wno-final-dtor-non-final-class -Wno-extra-semi-stmt -Wno-misleading-indentation -Wno-quoted-include-in-framework-header -Wno-implicit-fallthrough -Wno-enum-enum-conversion -Wno-enum-float-conversion -Wno-elaborated-enum-base -Wno-reserved-identifier -Wno-gnu-folding-constant -Wno-cast-function-type -Wno-bitwise-instead-of-logical --std=c++17 -fdeprecated-macro -fdebug-compilation-dir=/Users/phil/test_crap -ferror-limit 19 -stack-protector 1 -fstack-check -mdarwin-stkchk-strong-link -fblocks -fencode-extended-block-signature -fregister-global-dtors-with-atexit -fgnuc-version=4.2.1 -fno-cxx-modules -fcxx-exceptions -fexceptions -fmax-type-align=16 -fcommon -fcolor-diagnostics -clang-vendor-feature=+messageToSelfInClassMethodIdReturnType -clang-vendor-feature=+disableInferNewAvailabilityFromInit -clang-vendor-feature=+disableNonDependentMemberExprInCurrentInstantiation -fno-odr-hash-protocols -clang-vendor-feature=+enableAggressiveVLAFolding -clang-vendor-feature=+revert09abecef7bbf -clang-vendor-feature=+thisNoAlignAttr -clang-vendor-feature=+thisNoNullAttr -mllvm -disable-aligned-alloc-awareness=1 -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o /var/folders/n4/lyzh1r8n1wl77pqsjpm6xm440000gn/T/solution-945b01.o -x c++ solution.cpp clang -cc1 version 14.0.0 (clang-1400.0.29.102) default target arm64-apple-darwin21.6.0 ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local/include" ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/Library/Frameworks" #include "..." search starts here: #include <...> search starts here: /usr/local/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/14.0.0/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks (framework directory) End of search list. "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld" -demangle -lto_library /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libLTO.dylib -no_deduplicate -dynamic -arch arm64 -platform_version macos 12.0.0 12.3 -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -o a.out -L/usr/local/lib /var/folders/n4/lyzh1r8n1wl77pqsjpm6xm440000gn/T/solution-945b01.o -lc++ -lSystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/14.0.0/lib/darwin/libclang_rt.osx.a I think the error is maybe actually coming from the linker. g++ --verbose doesn't pass --verbose to the linker, but I know there is some magic invocation that will do that. See if you can find it.
Sep ’22
Reply to Xcode 14 update has bugs and my code in c++ is not compiling with memory issues.
but I am getting the same error how do I rectify that? thanks! Start by using the Xcode g++ (which is actually clang), not the homebrew g++. I'm not sure what the best way to do that is; I do have a lot of homebrew packages installed but not any compilers. If you want to have both homebrew and xcode compilers installed it may be sufficient to adjust your PATH - or it may not. I bet this is a Homebrew FAQ. Or, if you want to get the homebrew compiler working, try asking the homebrew people at e.g. https://github.com/Homebrew/discussions/discussions Curious to know if @fanick is using the Homebrew g++, deliberately or not?
Sep ’22