-
Bug
-
Resolution: Fixed
-
P2
-
7u40
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8034338 | 7u65 | David Dehaven | P2 | Resolved | Fixed | b01 |
JDK-8021852 | 7u60 | David Dehaven | P2 | Resolved | Fixed | b01 |
JDK-8022363 | 7u51 | David Dehaven | P2 | Resolved | Fixed | b01 |
JDK-8022000 | 7u45 | David Dehaven | P2 | Closed | Fixed | b05 |
JDK-8021584 | 7u40 | David Dehaven | P2 | Resolved | Fixed | b36 |
This was filed through JavaFX JIRA but since the issue is in JDK and not JavaFX I'm re-filing in JBS.
Original report:
While sending packager-deployed test application to Mac App Store, I met some issue with non-public API, which is prohibited by Mac App Store rules.
When I submit application with Application Loader it passes all the validation checks, then it's going to be hand-checked by Apple. Here is the failure. The report from Apple is:
2.5
The use of non-public APIs can lead to a poor user experience should these APIs change in the future, and is therefore not permitted. The app includes _CFBundleFlushBundleCaches from the framework '/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation'.
If you have defined a method in your source code with the same name as this API, we suggest altering your method name so that it no longer collides with Apple's private API to avoid your application being flagged in future submissions.
Alternatively, this API may reside in a library included with your application. If you do not have access to the library's source, you may be able to search the compiled binary using "strings" or "otool" command line tools. The "strings" tool can output a list of the methods that the library calls and "otool -ov" will output the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.
This bug blocks submitting to App Store.
Original report:
While sending packager-deployed test application to Mac App Store, I met some issue with non-public API, which is prohibited by Mac App Store rules.
When I submit application with Application Loader it passes all the validation checks, then it's going to be hand-checked by Apple. Here is the failure. The report from Apple is:
2.5
The use of non-public APIs can lead to a poor user experience should these APIs change in the future, and is therefore not permitted. The app includes _CFBundleFlushBundleCaches from the framework '/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation'.
If you have defined a method in your source code with the same name as this API, we suggest altering your method name so that it no longer collides with Apple's private API to avoid your application being flagged in future submissions.
Alternatively, this API may reside in a library included with your application. If you do not have access to the library's source, you may be able to search the compiled binary using "strings" or "otool" command line tools. The "strings" tool can output a list of the methods that the library calls and "otool -ov" will output the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.
This bug blocks submitting to App Store.
- backported by
-
JDK-8021584 Apple rejects deployed application as it's using non-public API
-
- Resolved
-
-
JDK-8021852 Apple rejects deployed application as it's using non-public API
-
- Resolved
-
-
JDK-8022363 Apple rejects deployed application as it's using non-public API
-
- Resolved
-
-
JDK-8034338 Apple rejects deployed application as it's using non-public API
-
- Resolved
-
-
JDK-8022000 Apple rejects deployed application as it's using non-public API
-
- Closed
-